Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e8b8945684783b5308a15549dcc3068a6c52ab511e47c2b9df081c4105aa66a2

Tx prefix hash: 42254d1320000bad8e392d9ca595eca82134bbe980039fa0293f0c301361aa20
Tx public key: f8725f78f7a3c1f4016fd3267d1fc8594d0b66aed2daea11f36605457eb71ae5
Timestamp: 1759894023 Timestamp [UCT]: 2025-10-08 03:27:03 Age [y:d:h:m:s]: 00:043:04:40:55
Block: 1385169 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 30939 RingCT/type: yes/0
Extra: 01f8725f78f7a3c1f4016fd3267d1fc8594d0b66aed2daea11f36605457eb71ae5021100000002a5dccd79000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e1433e537b05cb59d12e7af559b7da273893a762e583c5cc831c1d1418f4f2d2 0.600000000000 1873328 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": 1385179, "vin": [ { "gen": { "height": 1385169 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e1433e537b05cb59d12e7af559b7da273893a762e583c5cc831c1d1418f4f2d2" } } ], "extra": [ 1, 248, 114, 95, 120, 247, 163, 193, 244, 1, 111, 211, 38, 125, 31, 200, 89, 77, 11, 102, 174, 210, 218, 234, 17, 243, 102, 5, 69, 126, 183, 26, 229, 2, 17, 0, 0, 0, 2, 165, 220, 205, 121, 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