Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db6042d4c2956d44a548afad0cd25f221d2de4919edc20774f0119668441a00d

Tx prefix hash: 6a6c79d3b196f973c9175d961a391ac31068cfa76e2a224b0a0bd9fe7cb74f1c
Tx public key: 8acfd295fb4ec19121f59ae77d19f375f6ffedd75bbc423ad00f5505268d8ad1
Timestamp: 1713675233 Timestamp [UCT]: 2024-04-21 04:53:53 Age [y:d:h:m:s]: 00:224:05:41:37
Block: 1005109 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160545 RingCT/type: yes/0
Extra: 018acfd295fb4ec19121f59ae77d19f375f6ffedd75bbc423ad00f5505268d8ad102110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 60a4d6adcf1b1be025e01cc6cc93099cccfe55965f972b80986029606a1a67a1 0.600000000000 1465689 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": 1005119, "vin": [ { "gen": { "height": 1005109 } } ], "vout": [ { "amount": 600000000, "target": { "key": "60a4d6adcf1b1be025e01cc6cc93099cccfe55965f972b80986029606a1a67a1" } } ], "extra": [ 1, 138, 207, 210, 149, 251, 78, 193, 145, 33, 245, 154, 231, 125, 25, 243, 117, 246, 255, 237, 215, 91, 188, 66, 58, 208, 15, 85, 5, 38, 141, 138, 209, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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