Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: adb63f07885c9592dd5ff45f264e0b77271bf4bbec9341756f82e60882cee6b9

Tx prefix hash: 00bee50d98cd6dfc3d1dfbddc4d9326a9af9b2afbca26117393cf4d3176f7d07
Tx public key: 366a6cad4d9f70f9bc6e65709030ab8a681aa57ac277c40418b383543853b83d
Timestamp: 1732331300 Timestamp [UCT]: 2024-11-23 03:08:20 Age [y:d:h:m:s]: 00:001:02:24:08
Block: 1159690 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 786 RingCT/type: yes/0
Extra: 01366a6cad4d9f70f9bc6e65709030ab8a681aa57ac277c40418b383543853b83d021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 30a4f5764e2b2117893393cafd3d2dbb4c9f6737bb6b94c05f04c9acfdb3def4 0.600000000000 1645329 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": 1159700, "vin": [ { "gen": { "height": 1159690 } } ], "vout": [ { "amount": 600000000, "target": { "key": "30a4f5764e2b2117893393cafd3d2dbb4c9f6737bb6b94c05f04c9acfdb3def4" } } ], "extra": [ 1, 54, 106, 108, 173, 77, 159, 112, 249, 188, 110, 101, 112, 144, 48, 171, 138, 104, 26, 165, 122, 194, 119, 196, 4, 24, 179, 131, 84, 56, 83, 184, 61, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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