Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 94be662c842121031f85bc22b13996cb3d0913ff4c9ec5cba7ec933b6f429dd1

Tx prefix hash: dadeae2ade8f66c95dbb99f0704b444506962292390943e06f20dd4cd2d90257
Tx public key: 7ca26b5369f824ef56d4e3fc8f4a760d256cdbe5a7ba3ae264a6fc7c64f88546
Timestamp: 1718211396 Timestamp [UCT]: 2024-06-12 16:56:36 Age [y:d:h:m:s]: 00:301:13:04:57
Block: 1042729 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 215494 RingCT/type: yes/0
Extra: 017ca26b5369f824ef56d4e3fc8f4a760d256cdbe5a7ba3ae264a6fc7c64f885460211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6b21511742587941f3a40dd9c1d6c7a516f4820d42be0f6b49c2431b50a7420d 0.600000000000 1511716 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": 1042739, "vin": [ { "gen": { "height": 1042729 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6b21511742587941f3a40dd9c1d6c7a516f4820d42be0f6b49c2431b50a7420d" } } ], "extra": [ 1, 124, 162, 107, 83, 105, 248, 36, 239, 86, 212, 227, 252, 143, 74, 118, 13, 37, 108, 219, 229, 167, 186, 58, 226, 100, 166, 252, 124, 100, 248, 133, 70, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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