Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 36c540b84edd28d3cb1254c2476a75b15c7f8b8f2bec45d95dd23b2d705ce922

Tx prefix hash: e3001827875bc41ad3b26e20cc63d7f26514b1adc6e71c0f6a7d98019810d85e
Tx public key: ee08106f81afec6ad5675e493e6441a9251328e0a517076f04bd614b706acc07
Timestamp: 1711928680 Timestamp [UCT]: 2024-03-31 23:44:40 Age [y:d:h:m:s]: 01:216:23:14:41
Block: 990659 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 413716 RingCT/type: yes/0
Extra: 01ee08106f81afec6ad5675e493e6441a9251328e0a517076f04bd614b706acc0702110000000952d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eb7e1c8aff4ff3640b38463f5ab9e3fc8dd3cabcd004dbf119a2f042c14ca55d 0.600000000000 1450983 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": 990669, "vin": [ { "gen": { "height": 990659 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eb7e1c8aff4ff3640b38463f5ab9e3fc8dd3cabcd004dbf119a2f042c14ca55d" } } ], "extra": [ 1, 238, 8, 16, 111, 129, 175, 236, 106, 213, 103, 94, 73, 62, 100, 65, 169, 37, 19, 40, 224, 165, 23, 7, 111, 4, 189, 97, 75, 112, 106, 204, 7, 2, 17, 0, 0, 0, 9, 82, 212, 126, 148, 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