Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 716455416d6c223516e308846dafe55bb39561dadc8e9c6f60b3208df0032f28

Tx prefix hash: 26ce62b3c084ad84bcb85b2ee94fbe78ecc5234ececf5e3ea0c43c369ec0eaa1
Tx public key: 5ba9256d9f2b5c5ba30d93b12967846bd62a0677c46b507efa9072c0db8f23a8
Timestamp: 1710719119 Timestamp [UCT]: 2024-03-17 23:45:19 Age [y:d:h:m:s]: 01:231:22:19:40
Block: 980627 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 424436 RingCT/type: yes/0
Extra: 015ba9256d9f2b5c5ba30d93b12967846bd62a0677c46b507efa9072c0db8f23a802110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a3291451fa9a9b9664cd53c1a14e618d730dce3544e124220da4d5c645ba7d9a 0.600000000000 1440708 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": 980637, "vin": [ { "gen": { "height": 980627 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a3291451fa9a9b9664cd53c1a14e618d730dce3544e124220da4d5c645ba7d9a" } } ], "extra": [ 1, 91, 169, 37, 109, 159, 43, 92, 91, 163, 13, 147, 177, 41, 103, 132, 107, 214, 42, 6, 119, 196, 107, 80, 126, 250, 144, 114, 192, 219, 143, 35, 168, 2, 17, 0, 0, 0, 5, 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