Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ea18f9397db97aa3a79d9982fb064815f4cf576b5577f274ba36c697abc07085

Tx prefix hash: 85691991ba9d17c14b6c684f39c93d365c46f2132bb3163f2443135a8da09049
Tx public key: bc473ea861dceb7db435c7f87fa29b7e07ce7c3fca9d387cd7ae987db84540a3
Timestamp: 1727591902 Timestamp [UCT]: 2024-09-29 06:38:22 Age [y:d:h:m:s]: 00:234:19:41:23
Block: 1120503 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 167672 RingCT/type: yes/0
Extra: 01bc473ea861dceb7db435c7f87fa29b7e07ce7c3fca9d387cd7ae987db84540a3021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fde20736d42362f5b5c72bbd119e5dbe1397a6a7f4a3ece3f19870d1005fe1ac 0.600000000000 1602442 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": 1120513, "vin": [ { "gen": { "height": 1120503 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fde20736d42362f5b5c72bbd119e5dbe1397a6a7f4a3ece3f19870d1005fe1ac" } } ], "extra": [ 1, 188, 71, 62, 168, 97, 220, 235, 125, 180, 53, 199, 248, 127, 162, 155, 126, 7, 206, 124, 63, 202, 157, 56, 124, 215, 174, 152, 125, 184, 69, 64, 163, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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