Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4254e9d8a4c53303c2f823cb0fb0c99e3bb5388df4f4070503eb73b86355032e

Tx prefix hash: 0cb9cd4c532da996b728c50a369c4ebbb08f0a6ad8264ef8f8060bb8fbb09bc6
Tx public key: 653e0749a6f98706d762f7e0e561991bc163c0157face9272d07660a2cbd70d5
Timestamp: 1728948431 Timestamp [UCT]: 2024-10-14 23:27:11 Age [y:d:h:m:s]: 00:198:15:40:56
Block: 1131744 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 141766 RingCT/type: yes/0
Extra: 01653e0749a6f98706d762f7e0e561991bc163c0157face9272d07660a2cbd70d5021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3b9e0e314b30df3a85677723bee1294a753f96d7e714b4cc9ed7441b5dc1ae54 0.600000000000 1614649 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": 1131754, "vin": [ { "gen": { "height": 1131744 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3b9e0e314b30df3a85677723bee1294a753f96d7e714b4cc9ed7441b5dc1ae54" } } ], "extra": [ 1, 101, 62, 7, 73, 166, 249, 135, 6, 215, 98, 247, 224, 229, 97, 153, 27, 193, 99, 192, 21, 127, 172, 233, 39, 45, 7, 102, 10, 44, 189, 112, 213, 2, 17, 0, 0, 0, 1, 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