Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c02948a05c7d8cf9a794eb3784ec2120fa029e54c9c4199f5d5a0290443b83c4

Tx prefix hash: 55af3b316d45c2691b845c7aa376b87461edeef9749e0597bdaa05a28ee82af7
Tx public key: 6cc131f3cbb8e252e6e60799c602c4e44dd9e4197a43e1cd97cb37c080500cb0
Timestamp: 1638794110 Timestamp [UCT]: 2021-12-06 12:35:10 Age [y:d:h:m:s]: 02:348:20:54:10
Block: 389664 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 767357 RingCT/type: yes/0
Extra: 016cc131f3cbb8e252e6e60799c602c4e44dd9e4197a43e1cd97cb37c080500cb0021100000002e59f5d07000000000000000000

1 output(s) for total of 31.396539081000 dcy

stealth address amount amount idx
00: 612e70c2c38da3c2d01279be6ad8c37312e7572547b04827829b7965a92b18e1 31.396539081000 784951 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": 389674, "vin": [ { "gen": { "height": 389664 } } ], "vout": [ { "amount": 31396539081, "target": { "key": "612e70c2c38da3c2d01279be6ad8c37312e7572547b04827829b7965a92b18e1" } } ], "extra": [ 1, 108, 193, 49, 243, 203, 184, 226, 82, 230, 230, 7, 153, 198, 2, 196, 228, 77, 217, 228, 25, 122, 67, 225, 205, 151, 203, 55, 192, 128, 80, 12, 176, 2, 17, 0, 0, 0, 2, 229, 159, 93, 7, 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