Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3459a0c6d64d6af3e9013c9f862b9329c371897c34debc237c1fedb953b10f12

Tx prefix hash: 5e72cad160359c6a6325ec935f4b5cf213d65444f11dcfec9e62222e32036f54
Tx public key: a6c2fd87927437dc8fb60c23d5a6bd207bb6613cb20d60d8b9020e9bd42b5906
Timestamp: 1759430455 Timestamp [UCT]: 2025-10-02 18:40:55 Age [y:d:h:m:s]: 00:082:05:36:26
Block: 1381330 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 58878 RingCT/type: yes/0
Extra: 01a6c2fd87927437dc8fb60c23d5a6bd207bb6613cb20d60d8b9020e9bd42b590602110000000197baf922000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1778cbe126e862b11faf9eb211d3359493e6587365d1b8791aba26ec3e3c517a 0.600000000000 1869449 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": 1381340, "vin": [ { "gen": { "height": 1381330 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1778cbe126e862b11faf9eb211d3359493e6587365d1b8791aba26ec3e3c517a" } } ], "extra": [ 1, 166, 194, 253, 135, 146, 116, 55, 220, 143, 182, 12, 35, 213, 166, 189, 32, 123, 182, 97, 60, 178, 13, 96, 216, 185, 2, 14, 155, 212, 43, 89, 6, 2, 17, 0, 0, 0, 1, 151, 186, 249, 34, 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