Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c36b43bb556486f2c0d9e9c29cfe9d3c36f45a83c4b831b4c4546ab64e58177

Tx prefix hash: 49253479197151bc3a46f25bd274f5d164935a9fa844cf2dba7af286e046e4ce
Tx public key: 33408695e2f73accb3f12c69fbe743569c065dd2c0689a54ceb0ab4011c67014
Timestamp: 1732286188 Timestamp [UCT]: 2024-11-22 14:36:28 Age [y:d:h:m:s]: 00:001:15:19:59
Block: 1159317 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1172 RingCT/type: yes/0
Extra: 0133408695e2f73accb3f12c69fbe743569c065dd2c0689a54ceb0ab4011c670140211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9d8b0901cf51828fd54aecd0e500fca24a649e8d560aac4134ea307c012d4b1b 0.600000000000 1644950 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": 1159327, "vin": [ { "gen": { "height": 1159317 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9d8b0901cf51828fd54aecd0e500fca24a649e8d560aac4134ea307c012d4b1b" } } ], "extra": [ 1, 51, 64, 134, 149, 226, 247, 58, 204, 179, 241, 44, 105, 251, 231, 67, 86, 156, 6, 93, 210, 192, 104, 154, 84, 206, 176, 171, 64, 17, 198, 112, 20, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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