Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b6e44ddca5c4db3f9a29d0bd09e4930dce296743063acdfd5c246e58826593fa

Tx prefix hash: 7150f68333728f32b6edb0d0269c6dc2b19e1f479467bac2f88a0e92970ec74f
Tx public key: 7ed131423380e1e0c974be813ef5b85b73db3dc47e5341c96db338503f3c2029
Timestamp: 1738083790 Timestamp [UCT]: 2025-01-28 17:03:10 Age [y:d:h:m:s]: 00:361:15:04:00
Block: 1207063 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 256121 RingCT/type: yes/0
Extra: 017ed131423380e1e0c974be813ef5b85b73db3dc47e5341c96db338503f3c2029021100000003dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 535ae8f9c490138e5d3a85a0e3788b4246ac3e46ebe8146ce4f0620b95bf23c0 0.600000000000 1693784 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": 1207073, "vin": [ { "gen": { "height": 1207063 } } ], "vout": [ { "amount": 600000000, "target": { "key": "535ae8f9c490138e5d3a85a0e3788b4246ac3e46ebe8146ce4f0620b95bf23c0" } } ], "extra": [ 1, 126, 209, 49, 66, 51, 128, 225, 224, 201, 116, 190, 129, 62, 245, 184, 91, 115, 219, 61, 196, 126, 83, 65, 201, 109, 179, 56, 80, 63, 60, 32, 41, 2, 17, 0, 0, 0, 3, 223, 195, 186, 73, 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