Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2876517e8d548a82015fe1f359904df3b60ca545eccd8ccd5d0e0a761fc18c43

Tx prefix hash: ae1893e63449fdea02b914b71b177d96caad87000259125ad21d893fcd546c56
Tx public key: a11b99e92ebdf06a89d8cefa3d25c21dec2a574913f9cfed6ec9f5cce537a51e
Timestamp: 1659926463 Timestamp [UCT]: 2022-08-08 02:41:03 Age [y:d:h:m:s]: 02:280:14:56:56
Block: 561102 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 721799 RingCT/type: yes/0
Extra: 01a11b99e92ebdf06a89d8cefa3d25c21dec2a574913f9cfed6ec9f5cce537a51e021100000002ec6d1a1a000000000000000000

1 output(s) for total of 8.488603836000 dcy

stealth address amount amount idx
00: 3d9b29c352ec176e4425e5e4bab51e903a5a4d3eb9609d5349488a50ff9e31fc 8.488603836000 993392 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": 561112, "vin": [ { "gen": { "height": 561102 } } ], "vout": [ { "amount": 8488603836, "target": { "key": "3d9b29c352ec176e4425e5e4bab51e903a5a4d3eb9609d5349488a50ff9e31fc" } } ], "extra": [ 1, 161, 27, 153, 233, 46, 189, 240, 106, 137, 216, 206, 250, 61, 37, 194, 29, 236, 42, 87, 73, 19, 249, 207, 237, 110, 201, 245, 204, 229, 55, 165, 30, 2, 17, 0, 0, 0, 2, 236, 109, 26, 26, 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