Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4efbac9c16a9ef762a07d8d9238d4caaae686a73b7814e8494f2c673aaa0b617

Tx prefix hash: f52c23ac8edea8dbd820d474b91ce1053c6d12a7e503419a66e301517425b5d8
Tx public key: 7a10821ef3ad6a20f0aaf4f96aa20c7e8612b00925c496b2a4feb95075b80b09
Timestamp: 1727461065 Timestamp [UCT]: 2024-09-27 18:17:45 Age [y:d:h:m:s]: 00:222:02:48:15
Block: 1119411 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 158573 RingCT/type: yes/0
Extra: 017a10821ef3ad6a20f0aaf4f96aa20c7e8612b00925c496b2a4feb95075b80b0902110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2bb837573fc730eb2beabb9549acf51774bf7a22015f78855e9c29eabd5d92a0 0.600000000000 1600958 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": 1119421, "vin": [ { "gen": { "height": 1119411 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2bb837573fc730eb2beabb9549acf51774bf7a22015f78855e9c29eabd5d92a0" } } ], "extra": [ 1, 122, 16, 130, 30, 243, 173, 106, 32, 240, 170, 244, 249, 106, 162, 12, 126, 134, 18, 176, 9, 37, 196, 150, 178, 164, 254, 185, 80, 117, 184, 11, 9, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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