Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4d75fed6b789af0cb77ab68cc1c9d78dc1d9c7ac61a6ca955d74be7ee10cb63c

Tx prefix hash: 8261c775293fb1d49376605baa6edb255d17284f61368ffe5aa00d53f0a7a93d
Tx public key: b2c482181084a95c87f17a22e4bd5c517189291c4f907270f1667c50e58496a1
Timestamp: 1577180315 Timestamp [UCT]: 2019-12-24 09:38:35 Age [y:d:h:m:s]: 05:313:05:40:48
Block: 30555 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1371456 RingCT/type: yes/0
Extra: 01b2c482181084a95c87f17a22e4bd5c517189291c4f907270f1667c50e58496a102110000007ae39b962a000000000000000000

1 output(s) for total of 486.137879717000 dcy

stealth address amount amount idx
00: 90f65185afca8f7578eab14f9e723e8a3159a1f54c5e594c3a50bd32f7ef5fda 486.137879717000 50457 of 0

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": 30565, "vin": [ { "gen": { "height": 30555 } } ], "vout": [ { "amount": 486137879717, "target": { "key": "90f65185afca8f7578eab14f9e723e8a3159a1f54c5e594c3a50bd32f7ef5fda" } } ], "extra": [ 1, 178, 196, 130, 24, 16, 132, 169, 92, 135, 241, 122, 34, 228, 189, 92, 81, 113, 137, 41, 28, 79, 144, 114, 112, 241, 102, 124, 80, 229, 132, 150, 161, 2, 17, 0, 0, 0, 122, 227, 155, 150, 42, 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