Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9ee473a817ee3dedbbb9f797d1d742eaa9af136dbe246d17337f78c99978d739

Tx prefix hash: 9eca2007d290795a5b7aa0588f51d7346295679a6a3dd5cb2dd6cad0283dfe16
Tx public key: 5312e6c6cda51e9edf644c5a843ea5bef6b04ab30b67e629012c247e03216fe3
Timestamp: 1737296402 Timestamp [UCT]: 2025-01-19 14:20:02 Age [y:d:h:m:s]: 00:150:06:08:54
Block: 1200761 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107123 RingCT/type: yes/0
Extra: 015312e6c6cda51e9edf644c5a843ea5bef6b04ab30b67e629012c247e03216fe3021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 967c3ec83e7f70b21baadc383dbc3cb85004edc0b8189837c399e8d4d171cfdf 0.600000000000 1687406 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": 1200771, "vin": [ { "gen": { "height": 1200761 } } ], "vout": [ { "amount": 600000000, "target": { "key": "967c3ec83e7f70b21baadc383dbc3cb85004edc0b8189837c399e8d4d171cfdf" } } ], "extra": [ 1, 83, 18, 230, 198, 205, 165, 30, 158, 223, 100, 76, 90, 132, 62, 165, 190, 246, 176, 74, 179, 11, 103, 230, 41, 1, 44, 36, 126, 3, 33, 111, 227, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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