Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2b2aa6ce4afb45a5c16a4443a59cadcd0448cb4cedf59b54bd566a28815f7058

Tx prefix hash: b853d8fc7942338ef7be523d26c8a9e6d1f35a89b1653766c143aa2f95b04a03
Tx public key: 2081ca1442e452c2cdc5d6e6a2d013baca2837fceec74c0ffdd9dc37e9b73df3
Timestamp: 1762542036 Timestamp [UCT]: 2025-11-07 19:00:36 Age [y:d:h:m:s]: 00:046:03:41:25
Block: 1407124 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 33038 RingCT/type: yes/0
Extra: 012081ca1442e452c2cdc5d6e6a2d013baca2837fceec74c0ffdd9dc37e9b73df302110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 30bdcfdaf6a264bde581bd1eb7dbe44d46ebf9839c8e279490dc99a9c004f7bb 0.600000000000 1895531 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": 1407134, "vin": [ { "gen": { "height": 1407124 } } ], "vout": [ { "amount": 600000000, "target": { "key": "30bdcfdaf6a264bde581bd1eb7dbe44d46ebf9839c8e279490dc99a9c004f7bb" } } ], "extra": [ 1, 32, 129, 202, 20, 66, 228, 82, 194, 205, 197, 214, 230, 162, 208, 19, 186, 202, 40, 55, 252, 238, 199, 76, 15, 253, 217, 220, 55, 233, 183, 61, 243, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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