Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0040e525aa7043bad5173e0262f7cea2040bc1e1ab786778c18f6cf9d88c011b

Tx prefix hash: 5f5dc8ab82803baef4cb5f60974438a1e4d7ca039f8a7197d3c495688a252bec
Tx public key: 37c658fda245c537e7261df89aa0f6a23b9f97d3897c7eebb5f5b18daf8f859d
Timestamp: 1721032461 Timestamp [UCT]: 2024-07-15 08:34:21 Age [y:d:h:m:s]: 00:290:05:15:06
Block: 1066128 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 207342 RingCT/type: yes/0
Extra: 0137c658fda245c537e7261df89aa0f6a23b9f97d3897c7eebb5f5b18daf8f859d02110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 510f8d71e609109a29e14cf232608d7ef81fe013a63029d6049423f64c6ec01d 0.600000000000 1536701 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": 1066138, "vin": [ { "gen": { "height": 1066128 } } ], "vout": [ { "amount": 600000000, "target": { "key": "510f8d71e609109a29e14cf232608d7ef81fe013a63029d6049423f64c6ec01d" } } ], "extra": [ 1, 55, 198, 88, 253, 162, 69, 197, 55, 231, 38, 29, 248, 154, 160, 246, 162, 59, 159, 151, 211, 137, 124, 126, 235, 181, 245, 177, 141, 175, 143, 133, 157, 2, 17, 0, 0, 0, 7, 145, 225, 60, 4, 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