Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9d9f7d33b7f6db6565f04999581efa4d89720618fd4c887fa7452cc48f8dcf0d

Tx prefix hash: b0f95beb523671e213c1e80047967ab0ef9330c1853d16b38bb5c4d3082d6d05
Tx public key: dc6829bf4006d0b588c9a57fe788e57b7dec4d346da0f16f9b04ef8bdf23aac5
Timestamp: 1696870585 Timestamp [UCT]: 2023-10-09 16:56:25 Age [y:d:h:m:s]: 01:046:20:38:01
Block: 866011 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 294704 RingCT/type: yes/0
Extra: 01dc6829bf4006d0b588c9a57fe788e57b7dec4d346da0f16f9b04ef8bdf23aac502110000000575e3f0e9000000000000000000

1 output(s) for total of 0.828983892000 dcy

stealth address amount amount idx
00: 81de9c0db529ac742014f3c6c88fc8df26d2eab884ac80fc3e977024c6f02e6e 0.828983892000 1320577 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": 866021, "vin": [ { "gen": { "height": 866011 } } ], "vout": [ { "amount": 828983892, "target": { "key": "81de9c0db529ac742014f3c6c88fc8df26d2eab884ac80fc3e977024c6f02e6e" } } ], "extra": [ 1, 220, 104, 41, 191, 64, 6, 208, 181, 136, 201, 165, 127, 231, 136, 229, 123, 125, 236, 77, 52, 109, 160, 241, 111, 155, 4, 239, 139, 223, 35, 170, 197, 2, 17, 0, 0, 0, 5, 117, 227, 240, 233, 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