Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2c9beac12f79cec556637a9731189f40207e052c6fa8813d025e552e92bc6ed1

Tx prefix hash: db477dd15ab64d2b9a23b1c99942db70ee816e04119cbf1c33927427d597404d
Tx public key: 3c54d6f053f0a8f690dbb1e3f4a81b954f470ca4fdb370293b9e41877b13eec7
Timestamp: 1579178451 Timestamp [UCT]: 2020-01-16 12:40:51 Age [y:d:h:m:s]: 04:348:17:15:46
Block: 46823 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1138701 RingCT/type: yes/0
Extra: 013c54d6f053f0a8f690dbb1e3f4a81b954f470ca4fdb370293b9e41877b13eec70211000000098a2ee0d9000000000000000000

1 output(s) for total of 429.394820455000 dcy

stealth address amount amount idx
00: d58f0e742b130d48da959ace2d0b830cfd95179368ce1b273db3e1e6235dd9db 429.394820455000 86312 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": 46833, "vin": [ { "gen": { "height": 46823 } } ], "vout": [ { "amount": 429394820455, "target": { "key": "d58f0e742b130d48da959ace2d0b830cfd95179368ce1b273db3e1e6235dd9db" } } ], "extra": [ 1, 60, 84, 214, 240, 83, 240, 168, 246, 144, 219, 177, 227, 244, 168, 27, 149, 79, 71, 12, 164, 253, 179, 112, 41, 59, 158, 65, 135, 123, 19, 238, 199, 2, 17, 0, 0, 0, 9, 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