Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9a35e39e0da6bc3b8ada659b94be1486fd267d52e6246013bd51242b49625c6d

Tx prefix hash: 3824e23c5554b742437f7a4b1f5a980b255bb51aa4a662d9fb974d72634c4d17
Tx public key: eb1014d209e9f815a2f3d99274413925cf9f00af98767fb72451c1f1c134bbbc
Timestamp: 1708465011 Timestamp [UCT]: 2024-02-20 21:36:51 Age [y:d:h:m:s]: 01:253:19:32:51
Block: 961920 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 440150 RingCT/type: yes/0
Extra: 01eb1014d209e9f815a2f3d99274413925cf9f00af98767fb72451c1f1c134bbbc0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 124e4c1a2917d660e655cb5e2b1d2a9e47088591a61003b0c0d42842db0895c4 0.600000000000 1421537 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": 961930, "vin": [ { "gen": { "height": 961920 } } ], "vout": [ { "amount": 600000000, "target": { "key": "124e4c1a2917d660e655cb5e2b1d2a9e47088591a61003b0c0d42842db0895c4" } } ], "extra": [ 1, 235, 16, 20, 210, 9, 233, 248, 21, 162, 243, 217, 146, 116, 65, 57, 37, 207, 159, 0, 175, 152, 118, 127, 183, 36, 81, 193, 241, 193, 52, 187, 188, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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