Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 464b64407419a537d96bf0df579710e079e4d18701e1cfc7d0d1b87b17101be8

Tx prefix hash: b48f032a66a9c330919dc2d496c1c271504d217e1aca396ccc60af0159636faa
Tx public key: 706a02f6989427bc2d08d77849a1a633e237062924f4045dfabbb8e21079a4ed
Timestamp: 1749435247 Timestamp [UCT]: 2025-06-09 02:14:07 Age [y:d:h:m:s]: 00:153:12:00:23
Block: 1301046 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107368 RingCT/type: yes/0
Extra: 01706a02f6989427bc2d08d77849a1a633e237062924f4045dfabbb8e21079a4ed021100000004bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 00a5bd6c8cdf8afd8ea5c6c87691875fe7c7fc309727d74f8aa6ec0d8acbe122 0.600000000000 1788599 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": 1301056, "vin": [ { "gen": { "height": 1301046 } } ], "vout": [ { "amount": 600000000, "target": { "key": "00a5bd6c8cdf8afd8ea5c6c87691875fe7c7fc309727d74f8aa6ec0d8acbe122" } } ], "extra": [ 1, 112, 106, 2, 246, 152, 148, 39, 188, 45, 8, 215, 120, 73, 161, 166, 51, 226, 55, 6, 41, 36, 244, 4, 93, 250, 187, 184, 226, 16, 121, 164, 237, 2, 17, 0, 0, 0, 4, 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