Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 66a633def04bb3009c0a63e59ce344c5c18651988cf66588622db0e7cfa6e765

Tx prefix hash: dcc54c78f99f021274e028a5af9486ae6303e6f84489ca4a1554d0ab5a4f3512
Tx public key: 1c46390f425ab888a7c3a2c313a063bcd4935a8c63316d95db5aac31573c90c6
Timestamp: 1711360511 Timestamp [UCT]: 2024-03-25 09:55:11 Age [y:d:h:m:s]: 00:357:01:44:09
Block: 985958 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 255292 RingCT/type: yes/0
Extra: 011c46390f425ab888a7c3a2c313a063bcd4935a8c63316d95db5aac31573c90c602110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e4959ec25bab7558084195b0af1f0a5ad80e43a5cf2ffb6b556aa5cd53a4ea40 0.600000000000 1446179 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": 985968, "vin": [ { "gen": { "height": 985958 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e4959ec25bab7558084195b0af1f0a5ad80e43a5cf2ffb6b556aa5cd53a4ea40" } } ], "extra": [ 1, 28, 70, 57, 15, 66, 90, 184, 136, 167, 195, 162, 195, 19, 160, 99, 188, 212, 147, 90, 140, 99, 49, 109, 149, 219, 90, 172, 49, 87, 60, 144, 198, 2, 17, 0, 0, 0, 4, 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