Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8a95bae975d932e01f4d15bb7eace8d7f6b8db0dec3ac6ca37198112612459b6

Tx prefix hash: 5863e14b4d92ab8a1dcd27fc4ca0c1e4f88d90c6580ba8035825d561a489f806
Tx public key: 300e718d2eb089706e868a52eb24dbff07a5abf312e5bc19d4770e13d4ef8359
Timestamp: 1749258384 Timestamp [UCT]: 2025-06-07 01:06:24 Age [y:d:h:m:s]: 00:157:05:22:32
Block: 1299564 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110048 RingCT/type: yes/0
Extra: 01300e718d2eb089706e868a52eb24dbff07a5abf312e5bc19d4770e13d4ef8359021100000002bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f1b793e2caf4da6d40670e169a8b1f4bc3454f85bbd13bfc163ef480a1c0267d 0.600000000000 1787101 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": 1299574, "vin": [ { "gen": { "height": 1299564 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f1b793e2caf4da6d40670e169a8b1f4bc3454f85bbd13bfc163ef480a1c0267d" } } ], "extra": [ 1, 48, 14, 113, 141, 46, 176, 137, 112, 110, 134, 138, 82, 235, 36, 219, 255, 7, 165, 171, 243, 18, 229, 188, 25, 212, 119, 14, 19, 212, 239, 131, 89, 2, 17, 0, 0, 0, 2, 191, 81, 178, 162, 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