Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 31a6f6a41a66fe9cc506ad76f719719d05294e69ae50a377466ccd5d15eb8bb6

Tx prefix hash: 4ec4146e6f226fb3ad5e699887d5a1a93709f33dbeaf5b483de9b000c11f7d75
Tx public key: 09fe0d1d3dd95578b0378506569f43f1a3ba199aed23dbead0c5453d079987c6
Timestamp: 1713784303 Timestamp [UCT]: 2024-04-22 11:11:43 Age [y:d:h:m:s]: 00:206:15:00:53
Block: 1006023 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 147902 RingCT/type: yes/0
Extra: 0109fe0d1d3dd95578b0378506569f43f1a3ba199aed23dbead0c5453d079987c602110000000a59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d644256a89dbe9ca3ca65f2180a33b0b5bf71df1ecceec18e0f64e1ab04ba29e 0.600000000000 1466911 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": 1006033, "vin": [ { "gen": { "height": 1006023 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d644256a89dbe9ca3ca65f2180a33b0b5bf71df1ecceec18e0f64e1ab04ba29e" } } ], "extra": [ 1, 9, 254, 13, 29, 61, 217, 85, 120, 176, 55, 133, 6, 86, 159, 67, 241, 163, 186, 25, 154, 237, 35, 219, 234, 208, 197, 69, 61, 7, 153, 135, 198, 2, 17, 0, 0, 0, 10, 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