Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8838766628328c39c9d6ca3055c2e390c7b89b4dda25acf1debdcde700467703

Tx prefix hash: 9c1c8a23cf068b94e1f6112e221a3a185e05e33a428617c0e325fb9250988fa2
Tx public key: f880cebc544b0b35d7d91fe3686b725fd3f2f49686c7cb2fae55fbf8fab70387
Timestamp: 1751738295 Timestamp [UCT]: 2025-07-05 17:58:15 Age [y:d:h:m:s]: 00:127:13:33:42
Block: 1319413 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 89523 RingCT/type: yes/0
Extra: 01f880cebc544b0b35d7d91fe3686b725fd3f2f49686c7cb2fae55fbf8fab703870211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3d6fc1354707ca2581e28ade867502a97f4166d4439d01b83c4dcb9476a03699 0.600000000000 1807104 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": 1319423, "vin": [ { "gen": { "height": 1319413 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3d6fc1354707ca2581e28ade867502a97f4166d4439d01b83c4dcb9476a03699" } } ], "extra": [ 1, 248, 128, 206, 188, 84, 75, 11, 53, 215, 217, 31, 227, 104, 107, 114, 95, 211, 242, 244, 150, 134, 199, 203, 47, 174, 85, 251, 248, 250, 183, 3, 135, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 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