Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6011326cac01f91af40dd6e5ee9855c7b37186ae5b8a737ae557349ef194e25e

Tx prefix hash: 3e3f66a18999fdcd3c66f417bdfb24bacd41a1de4d5b4fc218dff0ddf7a6ff6d
Tx public key: cbe92b2520b866244680053282ad728cb872f49ed25bf2c4e78cf56f9c2f9bdd
Timestamp: 1749277287 Timestamp [UCT]: 2025-06-07 06:21:27 Age [y:d:h:m:s]: 00:157:07:08:19
Block: 1299729 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110098 RingCT/type: yes/0
Extra: 01cbe92b2520b866244680053282ad728cb872f49ed25bf2c4e78cf56f9c2f9bdd02110000000c43846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7ae64b9784d3b332f0f25738d193eb54ae20d3d97db965442f2e954e4ec38bf2 0.600000000000 1787268 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": 1299739, "vin": [ { "gen": { "height": 1299729 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7ae64b9784d3b332f0f25738d193eb54ae20d3d97db965442f2e954e4ec38bf2" } } ], "extra": [ 1, 203, 233, 43, 37, 32, 184, 102, 36, 70, 128, 5, 50, 130, 173, 114, 140, 184, 114, 244, 158, 210, 91, 242, 196, 231, 140, 245, 111, 156, 47, 155, 221, 2, 17, 0, 0, 0, 12, 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