Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 66c4eb0886bc9bbc084e7856192aac492379d7b741b13d306dd938a42b533f96

Tx prefix hash: 37697a2bec0cf8f3920a1b3d99476ca568b4e778194b64b67447a649c92643e8
Tx public key: 763c507e1b6bb3ae5776a910d9cfebd150af4a1ec9a80108e3fa51119f915baf
Timestamp: 1733295134 Timestamp [UCT]: 2024-12-04 06:52:14 Age [y:d:h:m:s]: 00:110:17:30:08
Block: 1167681 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 78926 RingCT/type: yes/0
Extra: 01763c507e1b6bb3ae5776a910d9cfebd150af4a1ec9a80108e3fa51119f915baf0211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ee5b6c1e356fe3f5251a39df0418f82de483b2ebf084186894afd503602165ad 0.600000000000 1653380 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": 1167691, "vin": [ { "gen": { "height": 1167681 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ee5b6c1e356fe3f5251a39df0418f82de483b2ebf084186894afd503602165ad" } } ], "extra": [ 1, 118, 60, 80, 126, 27, 107, 179, 174, 87, 118, 169, 16, 217, 207, 235, 209, 80, 175, 74, 30, 201, 168, 1, 8, 227, 250, 81, 17, 159, 145, 91, 175, 2, 17, 0, 0, 0, 7, 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