Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0daa8e62c5856a89ce3b7aa90886cb2e5d629614e1e959033d3744fc82927105

Tx prefix hash: a5dd535d0e4dba02d328ad76500707c74eda82767ae4f86313ae4b29e89f87b7
Tx public key: 5d15a455b4ad02b527e6452576b62a69c5ad6313c61310858d1af778ddd73fac
Timestamp: 1712273599 Timestamp [UCT]: 2024-04-04 23:33:19 Age [y:d:h:m:s]: 00:325:10:57:15
Block: 993486 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 232673 RingCT/type: yes/0
Extra: 015d15a455b4ad02b527e6452576b62a69c5ad6313c61310858d1af778ddd73fac02110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e87544dfe2f3e79f8e8f36e2fd151910caa6e3f7b7e2f0008b1cff65e9716061 0.600000000000 1453872 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": 993496, "vin": [ { "gen": { "height": 993486 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e87544dfe2f3e79f8e8f36e2fd151910caa6e3f7b7e2f0008b1cff65e9716061" } } ], "extra": [ 1, 93, 21, 164, 85, 180, 173, 2, 181, 39, 230, 69, 37, 118, 182, 42, 105, 197, 173, 99, 19, 198, 19, 16, 133, 141, 26, 247, 120, 221, 215, 63, 172, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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