Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a3d4bc819b44581cbfd63544ed64e27c63bc8eea90e96ffa7a5f5a72d8066fc6

Tx prefix hash: 69ac60b6e2816074c237c87c5a277734d6bcdb39b5b8e4cfb2e8af7567f57f9c
Tx public key: 8179f0011b90b059d6977a6589e7e15ee235364d0af215ec6cd61e64b1aa0a84
Timestamp: 1765916272 Timestamp [UCT]: 2025-12-16 20:17:52 Age [y:d:h:m:s]: 00:019:17:24:38
Block: 1435081 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 14137 RingCT/type: yes/0
Extra: 018179f0011b90b059d6977a6589e7e15ee235364d0af215ec6cd61e64b1aa0a840211000000037b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0bfb58d316e81f7b7f51e7add6b1fd0e81cccf4be468b72d229403d961d68a80 0.600000000000 1923878 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": 1435091, "vin": [ { "gen": { "height": 1435081 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0bfb58d316e81f7b7f51e7add6b1fd0e81cccf4be468b72d229403d961d68a80" } } ], "extra": [ 1, 129, 121, 240, 1, 27, 144, 176, 89, 214, 151, 122, 101, 137, 231, 225, 94, 226, 53, 54, 77, 10, 242, 21, 236, 108, 214, 30, 100, 177, 170, 10, 132, 2, 17, 0, 0, 0, 3, 123, 30, 81, 172, 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