Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 65a62df818929ff50c8513fb1a310ff42c8b0d5bda3d17e4a55440250ed18fbf

Tx prefix hash: aaef0b6c8064cfd34368feaa0ec7225ad37b86bc55b67882a8df92a2ac91f1b4
Tx public key: 0d7cf8e47005f81c2ee4b85c7fcb02fa13ca1579501e815ee5c5fd806987a4ef
Timestamp: 1692488810 Timestamp [UCT]: 2023-08-19 23:46:50 Age [y:d:h:m:s]: 02:094:20:09:12
Block: 829634 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 587543 RingCT/type: yes/0
Extra: 010d7cf8e47005f81c2ee4b85c7fcb02fa13ca1579501e815ee5c5fd806987a4ef02110000000375e3f0e9000000000000000000

1 output(s) for total of 1.094153483000 dcy

stealth address amount amount idx
00: f9669d66f90b3fb01c3fb8a976589f202ff14f3e1c2c4a026ed72ed9aeee32f1 1.094153483000 1282006 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": 829644, "vin": [ { "gen": { "height": 829634 } } ], "vout": [ { "amount": 1094153483, "target": { "key": "f9669d66f90b3fb01c3fb8a976589f202ff14f3e1c2c4a026ed72ed9aeee32f1" } } ], "extra": [ 1, 13, 124, 248, 228, 112, 5, 248, 28, 46, 228, 184, 92, 127, 203, 2, 250, 19, 202, 21, 121, 80, 30, 129, 94, 229, 197, 253, 128, 105, 135, 164, 239, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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