Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf8919cbfa06dc95a347ac3b04ef47b7df37335e5950213e748f395ba2204c23

Tx prefix hash: bbccf21e37a4a1c519cabcf24951263295d10364d3c2e0a7f1874aaf1ac88b9a
Tx public key: e95c0995bf2b1a4f3107cc5d0d8c7e8cd4432c629064edecb3137b8d36a00da7
Timestamp: 1646681557 Timestamp [UCT]: 2022-03-07 19:32:37 Age [y:d:h:m:s]: 02:322:11:35:24
Block: 453469 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 749935 RingCT/type: yes/0
Extra: 01e95c0995bf2b1a4f3107cc5d0d8c7e8cd4432c629064edecb3137b8d36a00da70211000000174da16a3a000000000000000000

1 output(s) for total of 19.296086297000 dcy

stealth address amount amount idx
00: 0b3d0e049e16c2b8707b47cee2a9274d734b7707227582e394613f764711412b 19.296086297000 868940 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": 453479, "vin": [ { "gen": { "height": 453469 } } ], "vout": [ { "amount": 19296086297, "target": { "key": "0b3d0e049e16c2b8707b47cee2a9274d734b7707227582e394613f764711412b" } } ], "extra": [ 1, 233, 92, 9, 149, 191, 43, 26, 79, 49, 7, 204, 93, 13, 140, 126, 140, 212, 67, 44, 98, 144, 100, 237, 236, 179, 19, 123, 141, 54, 160, 13, 167, 2, 17, 0, 0, 0, 23, 77, 161, 106, 58, 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