Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ee09e45dcda450a67102d55b92bd67b7b6b51ea5e3b97ef1d2dda6ba940c82fb

Tx prefix hash: 6aeb1934b0845bc22590fad6f769d283bfb164d0588bd8ac75cecb8d87a157f8
Tx public key: bcab5cf43ea18a3c25cf1adca2f49864ef9600474cc1cb7ee8fed2e08edb1de4
Timestamp: 1712899175 Timestamp [UCT]: 2024-04-12 05:19:35 Age [y:d:h:m:s]: 01:001:08:15:50
Block: 998666 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 261932 RingCT/type: yes/0
Extra: 01bcab5cf43ea18a3c25cf1adca2f49864ef9600474cc1cb7ee8fed2e08edb1de40211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 48171a3eff7bc17ffb288fffc8163cb4efec693019255c23c271fd849db451e9 0.600000000000 1459118 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": 998676, "vin": [ { "gen": { "height": 998666 } } ], "vout": [ { "amount": 600000000, "target": { "key": "48171a3eff7bc17ffb288fffc8163cb4efec693019255c23c271fd849db451e9" } } ], "extra": [ 1, 188, 171, 92, 244, 62, 161, 138, 60, 37, 207, 26, 220, 162, 244, 152, 100, 239, 150, 0, 71, 76, 193, 203, 126, 232, 254, 210, 224, 142, 219, 29, 228, 2, 17, 0, 0, 0, 2, 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