Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7ad471a767f6e43620ac966b2dd9f0815d50b3d8ef7a60506f15e1ad6c2b589e

Tx prefix hash: c04aa758f809a25b10a2a41a93acbcad3c4d08f5be19125d2d70e506b8d99ad6
Tx public key: e2a0f21750fb6141e3c362539e0c9aa8883b1d0258098ea1ccb61334c805140e
Timestamp: 1578805074 Timestamp [UCT]: 2020-01-12 04:57:54 Age [y:d:h:m:s]: 05:098:06:10:11
Block: 43664 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1220438 RingCT/type: yes/0
Extra: 01e2a0f21750fb6141e3c362539e0c9aa8883b1d0258098ea1ccb61334c805140e0211000000028a2ee0d9000000000000000000

1 output(s) for total of 439.869535339000 dcy

stealth address amount amount idx
00: d278931430de877feab5e1e0854c9b1e74901fed33623f221b069fa36d936c08 439.869535339000 79184 of 0

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": 43674, "vin": [ { "gen": { "height": 43664 } } ], "vout": [ { "amount": 439869535339, "target": { "key": "d278931430de877feab5e1e0854c9b1e74901fed33623f221b069fa36d936c08" } } ], "extra": [ 1, 226, 160, 242, 23, 80, 251, 97, 65, 227, 195, 98, 83, 158, 12, 154, 168, 136, 59, 29, 2, 88, 9, 142, 161, 204, 182, 19, 52, 200, 5, 20, 14, 2, 17, 0, 0, 0, 2, 138, 46, 224, 217, 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