Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc343f429993918c562a2f7aa896d0a7c23b491aa77db09477ff094691ac536c

Tx prefix hash: b9459a068c9724ed71237d3ca41e04aef94ea10baa677a68f4d8e750774eb013
Tx public key: 389b58580ce0b095ccae18f025ae43ffa3b8f61c1bea02c5363c7565689e3db6
Timestamp: 1710970019 Timestamp [UCT]: 2024-03-20 21:26:59 Age [y:d:h:m:s]: 01:028:17:20:31
Block: 982712 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 281502 RingCT/type: yes/0
Extra: 01389b58580ce0b095ccae18f025ae43ffa3b8f61c1bea02c5363c7565689e3db602110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1b9483a31a6a6bb733f63f0b8a2c1420a1fc41102d01eb839d486423d7f14116 0.600000000000 1442821 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": 982722, "vin": [ { "gen": { "height": 982712 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1b9483a31a6a6bb733f63f0b8a2c1420a1fc41102d01eb839d486423d7f14116" } } ], "extra": [ 1, 56, 155, 88, 88, 12, 224, 176, 149, 204, 174, 24, 240, 37, 174, 67, 255, 163, 184, 246, 28, 27, 234, 2, 197, 54, 60, 117, 101, 104, 158, 61, 182, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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