Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 64be942bbb353c0113406312dbf3c6d4de6ab9d5c538ce7376d7b917fa5420c3

Tx prefix hash: 3b26b12d300b4a55a46cf7f8d6be309fcdf37899255d36e1ff572894d5333ea5
Tx public key: f7ff6eacb5e5b6e4bf71d6a2493b1b34ca29c9e37176cd707093ee4dbbfe4ea9
Timestamp: 1638760702 Timestamp [UCT]: 2021-12-06 03:18:22 Age [y:d:h:m:s]: 03:024:11:59:48
Block: 389381 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 796420 RingCT/type: yes/0
Extra: 01f7ff6eacb5e5b6e4bf71d6a2493b1b34ca29c9e37176cd707093ee4dbbfe4ea9021100000001366b07f1000000000000000000

1 output(s) for total of 31.464401428000 dcy

stealth address amount amount idx
00: d04d60d1c9d9328ef4ad0037177e99b03fa86f14fd3ce34f0b4f0781e24d6502 31.464401428000 784512 of 0

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": 389391, "vin": [ { "gen": { "height": 389381 } } ], "vout": [ { "amount": 31464401428, "target": { "key": "d04d60d1c9d9328ef4ad0037177e99b03fa86f14fd3ce34f0b4f0781e24d6502" } } ], "extra": [ 1, 247, 255, 110, 172, 181, 229, 182, 228, 191, 113, 214, 162, 73, 59, 27, 52, 202, 41, 201, 227, 113, 118, 205, 112, 112, 147, 238, 77, 187, 254, 78, 169, 2, 17, 0, 0, 0, 1, 54, 107, 7, 241, 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