Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 825dd484b9e1929c555c902e82e965418b8850810ab67bdb1843c750b3b604b5

Tx prefix hash: 952550355b68cfb1722228348c41a313d4eec3c2cf0a5ba2ad3ed0a0fe6cf89c
Tx public key: 74b73c964c316edfb5e03f33b091d86a584e00a97dfbd25d1071e9cab07af3ee
Timestamp: 1750609712 Timestamp [UCT]: 2025-06-22 16:28:32 Age [y:d:h:m:s]: 00:150:04:01:51
Block: 1310564 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105198 RingCT/type: yes/0
Extra: 0174b73c964c316edfb5e03f33b091d86a584e00a97dfbd25d1071e9cab07af3ee02110000000243846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dc67e6ef24823d23ecaabf1218bab4b74fb408ac22fd213b7424579a65ca9a24 0.600000000000 1798185 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": 1310574, "vin": [ { "gen": { "height": 1310564 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dc67e6ef24823d23ecaabf1218bab4b74fb408ac22fd213b7424579a65ca9a24" } } ], "extra": [ 1, 116, 183, 60, 150, 76, 49, 110, 223, 181, 224, 63, 51, 176, 145, 216, 106, 88, 78, 0, 169, 125, 251, 210, 93, 16, 113, 233, 202, 176, 122, 243, 238, 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