Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 067085e5db1d5210b99c4de3dcb0642d829306d242db36e21eea7391a7bac6f2

Tx prefix hash: 4f273ca51770e92e49e2dcf55c4657a848cacb503c1387aab6498426259d5e7d
Tx public key: 29a0d16800127fb9bfb00ce62d351fec33b3e65bc0f7b2ae404c36aceefe0396
Timestamp: 1712574846 Timestamp [UCT]: 2024-04-08 11:14:06 Age [y:d:h:m:s]: 00:238:06:25:32
Block: 995969 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 170601 RingCT/type: yes/0
Extra: 0129a0d16800127fb9bfb00ce62d351fec33b3e65bc0f7b2ae404c36aceefe039602110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0dfd9545be004ac6e2bf8e21c61ea4ee0f9beda1707e39e259dab1e1f5b059e7 0.600000000000 1456385 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": 995979, "vin": [ { "gen": { "height": 995969 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0dfd9545be004ac6e2bf8e21c61ea4ee0f9beda1707e39e259dab1e1f5b059e7" } } ], "extra": [ 1, 41, 160, 209, 104, 0, 18, 127, 185, 191, 176, 12, 230, 45, 53, 31, 236, 51, 179, 230, 91, 192, 247, 178, 174, 64, 76, 54, 172, 238, 254, 3, 150, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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