Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c61f6ac1dbafb758c87f312bef5ebf760c38232b24b0d49410cc21faf35b677f

Tx prefix hash: bb6947961a8ad9a50fee4a1122acfe658947efc13b1e9e6c7bca44652adf5613
Tx public key: a7f9fc0b3d652c25b360c0bf8873aeccfefc3acfc4f39c07a1d6ddb257648ebe
Timestamp: 1711173543 Timestamp [UCT]: 2024-03-23 05:59:03 Age [y:d:h:m:s]: 01:222:13:27:09
Block: 984400 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 417738 RingCT/type: yes/0
Extra: 01a7f9fc0b3d652c25b360c0bf8873aeccfefc3acfc4f39c07a1d6ddb257648ebe0211000000030424019c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ee3e11f5d1d819ab97d81c230cc5eeeb08014cf3f85b8694914be9831e339b4d 0.600000000000 1444571 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": 984410, "vin": [ { "gen": { "height": 984400 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ee3e11f5d1d819ab97d81c230cc5eeeb08014cf3f85b8694914be9831e339b4d" } } ], "extra": [ 1, 167, 249, 252, 11, 61, 101, 44, 37, 179, 96, 192, 191, 136, 115, 174, 204, 254, 252, 58, 207, 196, 243, 156, 7, 161, 214, 221, 178, 87, 100, 142, 190, 2, 17, 0, 0, 0, 3, 4, 36, 1, 156, 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