Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4edb69d6daa8d0ad35eaa8da6ba5ed240f0458baa2125477d3515004371b82d0

Tx prefix hash: 6701351a15feca391411e02ac121022dd099b5e096d1e316761a400b9acbd768
Tx public key: d66a3c3af2cfc09e7194e4ee64e0a9900f23f9bb889d448922b1a6c808d7d863
Timestamp: 1706140530 Timestamp [UCT]: 2024-01-24 23:55:30 Age [y:d:h:m:s]: 01:293:15:53:24
Block: 942622 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 468702 RingCT/type: yes/0
Extra: 01d66a3c3af2cfc09e7194e4ee64e0a9900f23f9bb889d448922b1a6c808d7d8630211000000049da8e134000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2857c872d8cd07d82dfac6cd9a0ed13fa34faf59c6679bd01bf82dfffa1a0f01 0.600000000000 1400798 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": 942632, "vin": [ { "gen": { "height": 942622 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2857c872d8cd07d82dfac6cd9a0ed13fa34faf59c6679bd01bf82dfffa1a0f01" } } ], "extra": [ 1, 214, 106, 60, 58, 242, 207, 192, 158, 113, 148, 228, 238, 100, 224, 169, 144, 15, 35, 249, 187, 136, 157, 68, 137, 34, 177, 166, 200, 8, 215, 216, 99, 2, 17, 0, 0, 0, 4, 157, 168, 225, 52, 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