Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c1de26c35b064c2f97b3e3df4ccf642a550cd34e16ae4f24652413dcd8a0efe8

Tx prefix hash: 418e7f8d09631782e1a079ff4d16a1b38ee00d2555d2f88822bee49b9b4e3785
Tx public key: a801971cb7d1bff14259f843ed74a66b72f6e11bdc9d07b4d95929a6cf4b64e8
Timestamp: 1751363285 Timestamp [UCT]: 2025-07-01 09:48:05 Age [y:d:h:m:s]: 00:139:12:17:20
Block: 1316457 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 97917 RingCT/type: yes/0
Extra: 01a801971cb7d1bff14259f843ed74a66b72f6e11bdc9d07b4d95929a6cf4b64e8021100000002dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 33ad42951dfac98639ac5db72acc013767e05aacd6a2ad54b05469b88a16dc0f 0.600000000000 1804118 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": 1316467, "vin": [ { "gen": { "height": 1316457 } } ], "vout": [ { "amount": 600000000, "target": { "key": "33ad42951dfac98639ac5db72acc013767e05aacd6a2ad54b05469b88a16dc0f" } } ], "extra": [ 1, 168, 1, 151, 28, 183, 209, 191, 241, 66, 89, 248, 67, 237, 116, 166, 107, 114, 246, 225, 27, 220, 157, 7, 180, 217, 89, 41, 166, 207, 75, 100, 232, 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