Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 28723477eb7f47217aa8a845ff25395726c4be68f3cca2ab25371ff1aa53203f

Tx prefix hash: f6f5fcedb9147a12224b4b531aeccc3404216d62c9f32738aa09927772edf708
Tx public key: d79f238e9e33959ba784f08615d73f87d8f150d447d1320e92ec6b073f3710d0
Timestamp: 1726495016 Timestamp [UCT]: 2024-09-16 13:56:56 Age [y:d:h:m:s]: 00:275:04:52:39
Block: 1111401 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 196426 RingCT/type: yes/0
Extra: 01d79f238e9e33959ba784f08615d73f87d8f150d447d1320e92ec6b073f3710d0021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d4294bd7894f2d9b0ed8d4a0ae1d0583e802b350e3a2adb40981ed526ef6bff9 0.600000000000 1590346 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": 1111411, "vin": [ { "gen": { "height": 1111401 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d4294bd7894f2d9b0ed8d4a0ae1d0583e802b350e3a2adb40981ed526ef6bff9" } } ], "extra": [ 1, 215, 159, 35, 142, 158, 51, 149, 155, 167, 132, 240, 134, 21, 215, 63, 135, 216, 241, 80, 212, 71, 209, 50, 14, 146, 236, 107, 7, 63, 55, 16, 208, 2, 17, 0, 0, 0, 3, 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