Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c85b8b367a038bb8491dfa7c998207295b993805c894ce571edbe2d1149978fd

Tx prefix hash: e4fff34082c7833559b733a394414a86be5a5886df2f29959a088a4fa8e5a3d9
Tx public key: 1915e389149192e8a17e17461e2fa5de6e8d3bdfeddb7738a3f8afc41f0a33e1
Timestamp: 1737237309 Timestamp [UCT]: 2025-01-18 21:55:09 Age [y:d:h:m:s]: 00:150:16:27:39
Block: 1200276 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107423 RingCT/type: yes/0
Extra: 011915e389149192e8a17e17461e2fa5de6e8d3bdfeddb7738a3f8afc41f0a33e10211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 14623563d4d01b17713894c1ec725d7a36f7c819f2d76a7ecd0555c64ad8633c 0.600000000000 1686919 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": 1200286, "vin": [ { "gen": { "height": 1200276 } } ], "vout": [ { "amount": 600000000, "target": { "key": "14623563d4d01b17713894c1ec725d7a36f7c819f2d76a7ecd0555c64ad8633c" } } ], "extra": [ 1, 25, 21, 227, 137, 20, 145, 146, 232, 161, 126, 23, 70, 30, 47, 165, 222, 110, 141, 59, 223, 237, 219, 119, 56, 163, 248, 175, 196, 31, 10, 51, 225, 2, 17, 0, 0, 0, 3, 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