Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 52eb21b3392db070e9256d5b7f4752e2e611d6e082e323c4cb3b76224412b44f

Tx prefix hash: f833b7e5bd6320462d4cf873a82ac6fe583d884e70ffdb72cf9e81832c9d17fc
Tx public key: 069b412c560a2080a60ec09d132104791249fa4b0c0f364ac8f764f4c5b8ee99
Timestamp: 1751613911 Timestamp [UCT]: 2025-07-04 07:25:11 Age [y:d:h:m:s]: 00:133:01:27:15
Block: 1318464 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 93376 RingCT/type: yes/0
Extra: 01069b412c560a2080a60ec09d132104791249fa4b0c0f364ac8f764f4c5b8ee9902110000000243846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 95f7d22b1ae9102e86373c0223ead4e32231bc533285bd4db39043687f952373 0.600000000000 1806145 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": 1318474, "vin": [ { "gen": { "height": 1318464 } } ], "vout": [ { "amount": 600000000, "target": { "key": "95f7d22b1ae9102e86373c0223ead4e32231bc533285bd4db39043687f952373" } } ], "extra": [ 1, 6, 155, 65, 44, 86, 10, 32, 128, 166, 14, 192, 157, 19, 33, 4, 121, 18, 73, 250, 75, 12, 15, 54, 74, 200, 247, 100, 244, 197, 184, 238, 153, 2, 17, 0, 0, 0, 2, 67, 132, 109, 102, 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