Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 606cc84712869b3e6a6e82c0ac947a6cf495ccd01cfef22f226cf9cbcfccb315

Tx prefix hash: 6859150196738278e57aa9e3214e91aade8d855c604b0b907ef1763008df044d
Tx public key: a0f2e6032a9fff2b1e47951cef4896edd8e3c673a6aa2386d6cfeeb4fd0cee3a
Timestamp: 1763435351 Timestamp [UCT]: 2025-11-18 03:09:11 Age [y:d:h:m:s]: 00:010:03:42:03
Block: 1414530 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 7270 RingCT/type: yes/0
Extra: 01a0f2e6032a9fff2b1e47951cef4896edd8e3c673a6aa2386d6cfeeb4fd0cee3a02110000000143b50471000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6a852908406a5c40e379e1d08db81965de2ca9947d1464b492af46c62f32d1e2 0.600000000000 1903021 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": 1414540, "vin": [ { "gen": { "height": 1414530 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6a852908406a5c40e379e1d08db81965de2ca9947d1464b492af46c62f32d1e2" } } ], "extra": [ 1, 160, 242, 230, 3, 42, 159, 255, 43, 30, 71, 149, 28, 239, 72, 150, 237, 216, 227, 198, 115, 166, 170, 35, 134, 214, 207, 238, 180, 253, 12, 238, 58, 2, 17, 0, 0, 0, 1, 67, 181, 4, 113, 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