Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b82c7f9483d0243f72f8f3ea0c5a494c46fe6708eb112d3a6029bd6c2c08da8d

Tx prefix hash: 3a631dc3f73a9ba2d0fa93f78db1afb9d5268a016e5dc2c0fc2136d335d3ab3a
Tx public key: ac5db80ab7ee7c1d64f53f773ec6df5e8946ead45eaf28915a9f830870ec255a
Timestamp: 1723624008 Timestamp [UCT]: 2024-08-14 08:26:48 Age [y:d:h:m:s]: 00:259:07:55:31
Block: 1087607 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 185221 RingCT/type: yes/0
Extra: 01ac5db80ab7ee7c1d64f53f773ec6df5e8946ead45eaf28915a9f830870ec255a02110000000ae914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3218fe657cc0b4f84ab11674e4a1af794d6a96e85c7e89c7a256e85cee91e7d9 0.600000000000 1562216 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": 1087617, "vin": [ { "gen": { "height": 1087607 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3218fe657cc0b4f84ab11674e4a1af794d6a96e85c7e89c7a256e85cee91e7d9" } } ], "extra": [ 1, 172, 93, 184, 10, 183, 238, 124, 29, 100, 245, 63, 119, 62, 198, 223, 94, 137, 70, 234, 212, 94, 175, 40, 145, 90, 159, 131, 8, 112, 236, 37, 90, 2, 17, 0, 0, 0, 10, 233, 20, 221, 21, 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