Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 9fae00bf28010afdd418f44bdeefd004a61a778edc00f6ff8f22a6a71e2c4991

Tx prefix hash: f3da7eeed884512cd9d614f99943d2d00c725f2c1283768df58b71f10def310c
Tx public key: d7778125b574e1ab86b814c64d16d3a134ddbee66a4abe0f39786fb4a0a0f78a
Timestamp: 1702967049 Timestamp [UCT]: 2023-12-19 06:24:09 Age [y:d:h:m:s]: 01:147:18:49:36
Block: 916354 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 366765 RingCT/type: yes/0
Extra: 01d7778125b574e1ab86b814c64d16d3a134ddbee66a4abe0f39786fb4a0a0f78a02110000000175e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ea9f1c988c6878ffbf2b1bed7cab4c36939237f16442de3ef7a2e635cac375c5 0.600000000000 1373854 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 916364, "vin": [ { "gen": { "height": 916354 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ea9f1c988c6878ffbf2b1bed7cab4c36939237f16442de3ef7a2e635cac375c5" } } ], "extra": [ 1, 215, 119, 129, 37, 181, 116, 225, 171, 134, 184, 20, 198, 77, 22, 211, 161, 52, 221, 190, 230, 106, 74, 190, 15, 57, 120, 111, 180, 160, 160, 247, 138, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8