Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ecf27de351059fbf6397ed9c0bb7b99bdda8a47e8daeb6233802373732c130a

Tx prefix hash: 8bd4d2fb80ca845eee0ca0b9648dc350a0d1f83e9305743ec48d732cbbe9ea36
Tx public key: e0e15c8df176b527dc843d52da1b7aa08836d872382c9bc81165997c89889600
Timestamp: 1708454013 Timestamp [UCT]: 2024-02-20 18:33:33 Age [y:d:h:m:s]: 01:052:02:26:58
Block: 961831 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 298264 RingCT/type: yes/0
Extra: 01e0e15c8df176b527dc843d52da1b7aa08836d872382c9bc81165997c898896000211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f18b39504ab2e42680c90745de81bbf43e13c8314efc58cf3bdf0b48dc861f9b 0.600000000000 1421444 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": 961841, "vin": [ { "gen": { "height": 961831 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f18b39504ab2e42680c90745de81bbf43e13c8314efc58cf3bdf0b48dc861f9b" } } ], "extra": [ 1, 224, 225, 92, 141, 241, 118, 181, 39, 220, 132, 61, 82, 218, 27, 122, 160, 136, 54, 216, 114, 56, 44, 155, 200, 17, 101, 153, 124, 137, 136, 150, 0, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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