Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 71f04602d7dbc03991b89575d8a11238274b9b6545892d8be539fd10bc602c8f

Tx prefix hash: 12ed8b2b57fa8862fb778f4dbb5e02550f67821d63a33c51fcb62ae6e9994755
Tx public key: 6d91a464b7428f2fdbc3c3a1dfc2c9e2df3d15aaaad9982b54d46e77b928d9f3
Timestamp: 1621611288 Timestamp [UCT]: 2021-05-21 15:34:48 Age [y:d:h:m:s]: 03:193:09:58:30
Block: 264601 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 900055 RingCT/type: yes/0
Extra: 016d91a464b7428f2fdbc3c3a1dfc2c9e2df3d15aaaad9982b54d46e77b928d9f302110000002367297a1c000000000000000000

1 output(s) for total of 81.520641313000 dcy

stealth address amount amount idx
00: 627060b37bc67f13724c1829ee03962fdca4d37b864e3d4640356e6d94d98796 81.520641313000 556359 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": 264611, "vin": [ { "gen": { "height": 264601 } } ], "vout": [ { "amount": 81520641313, "target": { "key": "627060b37bc67f13724c1829ee03962fdca4d37b864e3d4640356e6d94d98796" } } ], "extra": [ 1, 109, 145, 164, 100, 183, 66, 143, 47, 219, 195, 195, 161, 223, 194, 201, 226, 223, 61, 21, 170, 170, 217, 152, 43, 84, 212, 110, 119, 185, 40, 217, 243, 2, 17, 0, 0, 0, 35, 103, 41, 122, 28, 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