Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f1bec6162836232e98c6b97b5ff3eae90e2202c44a0bd76dee08c1214f75c3b

Tx prefix hash: c1c3eb1784875fd226dfbcc1493983c90554301e6100a8e78f2783dc4511517c
Tx public key: ef4ffdf20e1f48cde30d5bf7c2ebf8c9d28b2f14b7ed6f344a5a6d4e6f507eb5
Timestamp: 1725585815 Timestamp [UCT]: 2024-09-06 01:23:35 Age [y:d:h:m:s]: 00:079:14:41:19
Block: 1103867 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 56929 RingCT/type: yes/0
Extra: 01ef4ffdf20e1f48cde30d5bf7c2ebf8c9d28b2f14b7ed6f344a5a6d4e6f507eb502110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c821137e6cf146c1e8554b2571e9f6f89bbea8404bc262b686c042cc35007e47 0.600000000000 1580860 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": 1103877, "vin": [ { "gen": { "height": 1103867 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c821137e6cf146c1e8554b2571e9f6f89bbea8404bc262b686c042cc35007e47" } } ], "extra": [ 1, 239, 79, 253, 242, 14, 31, 72, 205, 227, 13, 91, 247, 194, 235, 248, 201, 210, 139, 47, 20, 183, 237, 111, 52, 74, 90, 109, 78, 111, 80, 126, 181, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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