Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 45e65a1c35b8b4382f9fb461848061fa1ef48f5eb7c894dba4468d6c0d80ba6b

Tx prefix hash: ce8fa8d792675204c18f575fbc308117d7f0595f9b4ca279f5f4b03806c00075
Tx public key: 470092402f6c17f1e447ecc74ae894e5dc2ad419b3405273559398fa82c0def2
Timestamp: 1766163307 Timestamp [UCT]: 2025-12-19 16:55:07 Age [y:d:h:m:s]: 00:003:03:25:24
Block: 1437145 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 2235 RingCT/type: yes/0
Extra: 01470092402f6c17f1e447ecc74ae894e5dc2ad419b3405273559398fa82c0def202110000000a7b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d1aba04d3639533ca52e2f414b8df1bdb8f2ec3ccb8605867805b25c2f59399f 0.600000000000 1925950 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": 1437155, "vin": [ { "gen": { "height": 1437145 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d1aba04d3639533ca52e2f414b8df1bdb8f2ec3ccb8605867805b25c2f59399f" } } ], "extra": [ 1, 71, 0, 146, 64, 47, 108, 23, 241, 228, 71, 236, 199, 74, 232, 148, 229, 220, 42, 212, 25, 179, 64, 82, 115, 85, 147, 152, 250, 130, 192, 222, 242, 2, 17, 0, 0, 0, 10, 123, 30, 81, 172, 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