Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fdd80449cbc01d9bef929032e392df279cb3c2eb5b1aa9bd881920382ed80b10

Tx prefix hash: 2bf124e5826a26a8133b4649fbd209487acc3f073e0517296077425c658905aa
Tx public key: f3a74c59e5b5981bff7e492e743cf645e59a6cfe6dfaf25fa5e555194d207ef6
Timestamp: 1748012350 Timestamp [UCT]: 2025-05-23 14:59:10 Age [y:d:h:m:s]: 00:224:21:52:34
Block: 1289255 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 158503 RingCT/type: yes/0
Extra: 01f3a74c59e5b5981bff7e492e743cf645e59a6cfe6dfaf25fa5e555194d207ef6021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2cd9d5b7d9162c6bbc6dea0536afe93ebe21fead521fab6b1b3c11db6a562b55 0.600000000000 1776722 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": 1289265, "vin": [ { "gen": { "height": 1289255 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2cd9d5b7d9162c6bbc6dea0536afe93ebe21fead521fab6b1b3c11db6a562b55" } } ], "extra": [ 1, 243, 167, 76, 89, 229, 181, 152, 27, 255, 126, 73, 46, 116, 60, 246, 69, 229, 154, 108, 254, 109, 250, 242, 95, 165, 229, 85, 25, 77, 32, 126, 246, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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