Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 259ec1f0697274ceedf58b5820f4a93f9f56c57d7d8d68aaee7f23e29c7867cb

Tx prefix hash: c06b46fd6609686d687cd51bba8fcbbcdd9fe0d0b9e1ef3e372b24547fb160c6
Tx public key: 94fedc4830ff1a2c68cd2db0fc868b008bfb97e912269a054d301fc4de32ee91
Timestamp: 1749720675 Timestamp [UCT]: 2025-06-12 09:31:15 Age [y:d:h:m:s]: 00:158:01:47:51
Block: 1303361 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110693 RingCT/type: yes/0
Extra: 0194fedc4830ff1a2c68cd2db0fc868b008bfb97e912269a054d301fc4de32ee91021100000003d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dc5158d39ea3e2bc6334f6642710c7da7e6977a2a69dfc91611b1b6e933e5e55 0.600000000000 1790940 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": 1303371, "vin": [ { "gen": { "height": 1303361 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dc5158d39ea3e2bc6334f6642710c7da7e6977a2a69dfc91611b1b6e933e5e55" } } ], "extra": [ 1, 148, 254, 220, 72, 48, 255, 26, 44, 104, 205, 45, 176, 252, 134, 139, 0, 139, 251, 151, 233, 18, 38, 154, 5, 77, 48, 31, 196, 222, 50, 238, 145, 2, 17, 0, 0, 0, 3, 216, 231, 210, 65, 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