Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ff62732e00f80f0e60a1638052b305307b2f0eda97fa08ccb980ac604701f3a5

Tx prefix hash: 39cf2b040a980e8ee3f86564a0f19e023d257bd75a1e33f147c8ff7937682425
Tx public key: 6ea93ea032a5ee818a4deb7f8f746f9fcba5396499b8375c1b695c7f1126f529
Timestamp: 1731227516 Timestamp [UCT]: 2024-11-10 08:31:56 Age [y:d:h:m:s]: 00:128:00:23:12
Block: 1150545 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 91323 RingCT/type: yes/0
Extra: 016ea93ea032a5ee818a4deb7f8f746f9fcba5396499b8375c1b695c7f1126f529021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7bf08336c0c1e185295d4664c8c44911899e965531460722a04168b8326e66ba 0.600000000000 1635892 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": 1150555, "vin": [ { "gen": { "height": 1150545 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7bf08336c0c1e185295d4664c8c44911899e965531460722a04168b8326e66ba" } } ], "extra": [ 1, 110, 169, 62, 160, 50, 165, 238, 129, 138, 77, 235, 127, 143, 116, 111, 159, 203, 165, 57, 100, 153, 184, 55, 92, 27, 105, 92, 127, 17, 38, 245, 41, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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