Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aaa5e1ff7b84ede895537e9536482d6c50572e415dfe13cf89d13bb878636753

Tx prefix hash: c266e59c90563484ff415ea821d6c41a662b152750de82ee2ffd757c837084ce
Tx public key: 76b1a7d9d55aa44e60edeaaf14657612446951ba9f2f5679c3f0fb262abd5039
Timestamp: 1722372717 Timestamp [UCT]: 2024-07-30 20:51:57 Age [y:d:h:m:s]: 00:085:01:32:25
Block: 1077222 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 60908 RingCT/type: yes/0
Extra: 0176b1a7d9d55aa44e60edeaaf14657612446951ba9f2f5679c3f0fb262abd503902110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a029bb670e923bbd925faaeacf0dffccb3e022c0d1696f958472e4d1dbf28e3c 0.600000000000 1549769 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": 1077232, "vin": [ { "gen": { "height": 1077222 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a029bb670e923bbd925faaeacf0dffccb3e022c0d1696f958472e4d1dbf28e3c" } } ], "extra": [ 1, 118, 177, 167, 217, 213, 90, 164, 78, 96, 237, 234, 175, 20, 101, 118, 18, 68, 105, 81, 186, 159, 47, 86, 121, 195, 240, 251, 38, 42, 189, 80, 57, 2, 17, 0, 0, 0, 8, 145, 225, 60, 4, 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