Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 05449bed21d9c60bbfe4198837dafe49193862bc6a69e4cab01edfb11273124e

Tx prefix hash: ba514a32eeadb838b981bc0e14c4ca6a843a0bb711e7dcd995299b424d04a4b3
Tx public key: 8ba3fec944bb4496c17710efe7a4b5fdd433806f6d8c5a7880b3f267a21e4c8f
Timestamp: 1750160900 Timestamp [UCT]: 2025-06-17 11:48:20 Age [y:d:h:m:s]: 00:228:22:59:49
Block: 1306938 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 161336 RingCT/type: yes/0
Extra: 018ba3fec944bb4496c17710efe7a4b5fdd433806f6d8c5a7880b3f267a21e4c8f021100000002dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a14905cc149eb83b083158a61c7c67650d5d1f0f1fdd4bc46ec7220e9844808f 0.600000000000 1794547 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": 1306948, "vin": [ { "gen": { "height": 1306938 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a14905cc149eb83b083158a61c7c67650d5d1f0f1fdd4bc46ec7220e9844808f" } } ], "extra": [ 1, 139, 163, 254, 201, 68, 187, 68, 150, 193, 119, 16, 239, 231, 164, 181, 253, 212, 51, 128, 111, 109, 140, 90, 120, 128, 179, 242, 103, 162, 30, 76, 143, 2, 17, 0, 0, 0, 2, 223, 195, 186, 73, 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