Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 38b8951b798f7eb4991334643ace23bd4fc6bb5769794321e5501603759574e5

Tx prefix hash: 4265213182426ec23f6dc32c88b1ec19ef59b429559ae0057ebe397f3ba28371
Tx public key: 3e4a9bf4f37c00f81f0f995a96761cc34ee4ac1c1e6a82f6a7c3cebae2eddd50
Timestamp: 1707350976 Timestamp [UCT]: 2024-02-08 00:09:36 Age [y:d:h:m:s]: 01:020:06:11:30
Block: 952673 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 275499 RingCT/type: yes/0
Extra: 013e4a9bf4f37c00f81f0f995a96761cc34ee4ac1c1e6a82f6a7c3cebae2eddd5002110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 28f4e73677869ee91aeb697df54b35f4d3b1d76f897d70c1c3a44d0bb318cb37 0.600000000000 1411773 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": 952683, "vin": [ { "gen": { "height": 952673 } } ], "vout": [ { "amount": 600000000, "target": { "key": "28f4e73677869ee91aeb697df54b35f4d3b1d76f897d70c1c3a44d0bb318cb37" } } ], "extra": [ 1, 62, 74, 155, 244, 243, 124, 0, 248, 31, 15, 153, 90, 150, 118, 28, 195, 78, 228, 172, 28, 30, 106, 130, 246, 167, 195, 206, 186, 226, 237, 221, 80, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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