Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eb4477b9ac1ca5a089a3641504e3dede47a6f51ff3f6174605a7beabbd1c25a2

Tx prefix hash: 7efc710f2c1e10e1e5e1c1b4a474c03f70d479367d66abf5b211fbcdf5bd8426
Tx public key: a77b3d427ead68068aba34d50984badb857fc32349e2947182f0f508b390f68d
Timestamp: 1718927148 Timestamp [UCT]: 2024-06-20 23:45:48 Age [y:d:h:m:s]: 00:302:00:25:57
Block: 1048656 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 215837 RingCT/type: yes/0
Extra: 01a77b3d427ead68068aba34d50984badb857fc32349e2947182f0f508b390f68d02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a3d741828c7da3b1f215a533664244a3c117d1ceac4fa6436839835dca363316 0.600000000000 1518741 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": 1048666, "vin": [ { "gen": { "height": 1048656 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a3d741828c7da3b1f215a533664244a3c117d1ceac4fa6436839835dca363316" } } ], "extra": [ 1, 167, 123, 61, 66, 126, 173, 104, 6, 138, 186, 52, 213, 9, 132, 186, 219, 133, 127, 195, 35, 73, 226, 148, 113, 130, 240, 245, 8, 179, 144, 246, 141, 2, 17, 0, 0, 0, 2, 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