Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e491089177066a37f1a07cc8f9f6140c38d5d29f055b5b4835a255e517aeff3e

Tx prefix hash: 917a69cc6961286b5e0eacdcc5405b36a6f0549fd603afd2a577221fde689895
Tx public key: ced168567b473c7a93e35af489909a1e1d94ac61a830f5ccd9d6014da515b01c
Timestamp: 1749339755 Timestamp [UCT]: 2025-06-07 23:42:35 Age [y:d:h:m:s]: 00:215:19:06:04
Block: 1300246 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 151991 RingCT/type: yes/0
Extra: 01ced168567b473c7a93e35af489909a1e1d94ac61a830f5ccd9d6014da515b01c02110000000843846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b4d0c835559f2e79ce8d63e165b421dc2c52c3a7ec8c460668ed008f708d6d8a 0.600000000000 1787795 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": 1300256, "vin": [ { "gen": { "height": 1300246 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b4d0c835559f2e79ce8d63e165b421dc2c52c3a7ec8c460668ed008f708d6d8a" } } ], "extra": [ 1, 206, 209, 104, 86, 123, 71, 60, 122, 147, 227, 90, 244, 137, 144, 154, 30, 29, 148, 172, 97, 168, 48, 245, 204, 217, 214, 1, 77, 165, 21, 176, 28, 2, 17, 0, 0, 0, 8, 67, 132, 109, 102, 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