Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0debf9928b202442fed931aa4688046ef716d306cd61a6aadf3e287029856251

Tx prefix hash: db83ff96178159ab0ebef6d0cacb3e3fbf85644862da15a7d60afabd0ee13992
Tx public key: 8ae479883a4960b68aa3b2c37cc7f41abc2d381d6c05f4e50bce35a7dbefe4f2
Timestamp: 1702500793 Timestamp [UCT]: 2023-12-13 20:53:13 Age [y:d:h:m:s]: 01:356:18:44:04
Block: 912476 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 513899 RingCT/type: yes/0
Extra: 018ae479883a4960b68aa3b2c37cc7f41abc2d381d6c05f4e50bce35a7dbefe4f2021100000003faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aa13fb586d771b3a16f8e369389a321bbf8528fb216264e8d67b578e389a1160 0.600000000000 1369704 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": 912486, "vin": [ { "gen": { "height": 912476 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aa13fb586d771b3a16f8e369389a321bbf8528fb216264e8d67b578e389a1160" } } ], "extra": [ 1, 138, 228, 121, 136, 58, 73, 96, 182, 138, 163, 178, 195, 124, 199, 244, 26, 188, 45, 56, 29, 108, 5, 244, 229, 11, 206, 53, 167, 219, 239, 228, 242, 2, 17, 0, 0, 0, 3, 250, 243, 92, 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