Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f293b446eb22208a4c5332f8903297e73a9d0c18422c25f7604c9fdf6f950e0a

Tx prefix hash: a643823e1c3b616a757e54ac64e3ad3674880558e1d19337a2d596585f87dc31
Tx public key: 6d6c1d946f5686058493e19379440200c56d82e9dfd1a706ca42cc542bc31a80
Timestamp: 1713159086 Timestamp [UCT]: 2024-04-15 05:31:26 Age [y:d:h:m:s]: 00:360:05:26:47
Block: 1000825 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 257545 RingCT/type: yes/0
Extra: 016d6c1d946f5686058493e19379440200c56d82e9dfd1a706ca42cc542bc31a800211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 370ac91e6b3d8b4be9af8d66da3b7e863f7a51dea1aa70ccadb7658e28acac28 0.600000000000 1461325 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": 1000835, "vin": [ { "gen": { "height": 1000825 } } ], "vout": [ { "amount": 600000000, "target": { "key": "370ac91e6b3d8b4be9af8d66da3b7e863f7a51dea1aa70ccadb7658e28acac28" } } ], "extra": [ 1, 109, 108, 29, 148, 111, 86, 134, 5, 132, 147, 225, 147, 121, 68, 2, 0, 197, 109, 130, 233, 223, 209, 167, 6, 202, 66, 204, 84, 43, 195, 26, 128, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 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