Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 456d26ac217d07e760a43f1a80cb459c943f6dd5b5595e43587447562b620b27

Tx prefix hash: 3c2631dc5d88342917a9ec97812c62bc2c2faa32fcf1ad7903a5f203a2278827
Tx public key: 360c5bc9adcf19af072fab92f971d125e215d9af0554d17cbd5f66d2f0300ac7
Timestamp: 1731228448 Timestamp [UCT]: 2024-11-10 08:47:28 Age [y:d:h:m:s]: 00:364:00:07:05
Block: 1150556 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 257700 RingCT/type: yes/0
Extra: 01360c5bc9adcf19af072fab92f971d125e215d9af0554d17cbd5f66d2f0300ac70211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 953d38ff347236ce1fbfab7fb0ee9037f41215a52400652e2f3b43221efe2cd1 0.600000000000 1635905 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": 1150566, "vin": [ { "gen": { "height": 1150556 } } ], "vout": [ { "amount": 600000000, "target": { "key": "953d38ff347236ce1fbfab7fb0ee9037f41215a52400652e2f3b43221efe2cd1" } } ], "extra": [ 1, 54, 12, 91, 201, 173, 207, 25, 175, 7, 47, 171, 146, 249, 113, 209, 37, 226, 21, 217, 175, 5, 84, 209, 124, 189, 95, 102, 210, 240, 48, 10, 199, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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