Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc1579a705e1a1676c3d7c50ee3c0eba79dd534db9f3e0a307dfa9871d9fecb7

Tx prefix hash: 3644103bdcacd1ac0ca46b08d4d2d866f93eed92b930a69af4018abf8907633a
Tx public key: d36f0dc782ced096fa9e071ea30f596c1f7a02ff5d91a81229de48fd429e73a0
Timestamp: 1686383280 Timestamp [UCT]: 2023-06-10 07:48:00 Age [y:d:h:m:s]: 01:307:23:57:56
Block: 779113 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 481305 RingCT/type: yes/0
Extra: 01d36f0dc782ced096fa9e071ea30f596c1f7a02ff5d91a81229de48fd429e73a002110000000433af99f4000000000000000000

1 output(s) for total of 1.608701128000 dcy

stealth address amount amount idx
00: 5f4f3327e4a77cdec7e0ec10c9ddec4d7dd22c60768e035d29dd5ed47ae2981f 1.608701128000 1228758 of 0

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": 779123, "vin": [ { "gen": { "height": 779113 } } ], "vout": [ { "amount": 1608701128, "target": { "key": "5f4f3327e4a77cdec7e0ec10c9ddec4d7dd22c60768e035d29dd5ed47ae2981f" } } ], "extra": [ 1, 211, 111, 13, 199, 130, 206, 208, 150, 250, 158, 7, 30, 163, 15, 89, 108, 31, 122, 2, 255, 93, 145, 168, 18, 41, 222, 72, 253, 66, 158, 115, 160, 2, 17, 0, 0, 0, 4, 51, 175, 153, 244, 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