Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb84712d59b7e225b8208e3911caf1d3a5b9c1a7771120eacfcff525a95d2322

Tx prefix hash: 9f117eb0e612ed871dffe5d3c433046ed3fb7c172c45a1b0748a7f99cb172c87
Tx public key: 491d29b6f847a8dc8bb0485916c9cb55ebf80dd5b1712d5ee0daab119ea0a397
Timestamp: 1574390884 Timestamp [UCT]: 2019-11-22 02:48:04 Age [y:d:h:m:s]: 05:343:23:55:17
Block: 14132 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0986 kB
Tx version: 2 No of confirmations: 1386790 RingCT/type: yes/0
Extra: 01491d29b6f847a8dc8bb0485916c9cb55ebf80dd5b1712d5ee0daab119ea0a39702110000000166a80d00000000000000000000

1 output(s) for total of 551.030582312000 dcy

stealth address amount amount idx
00: 04cc63a17a04e85ca9509606f6ce3d039d1aa4c5d7fd4a98cf2d48fb70f5f696 551.030582312000 17526 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": 14142, "vin": [ { "gen": { "height": 14132 } } ], "vout": [ { "amount": 551030582312, "target": { "key": "04cc63a17a04e85ca9509606f6ce3d039d1aa4c5d7fd4a98cf2d48fb70f5f696" } } ], "extra": [ 1, 73, 29, 41, 182, 248, 71, 168, 220, 139, 176, 72, 89, 22, 201, 203, 85, 235, 248, 13, 213, 177, 113, 45, 94, 224, 218, 171, 17, 158, 160, 163, 151, 2, 17, 0, 0, 0, 1, 102, 168, 13, 0, 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