Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6c2076c55698f547eaa9361d105ebe1996ff03d13d5ff5e66c90a7fb3aa48219

Tx prefix hash: a6642dad3cc09111a1f0ab1ccf8f222ae6cf925b2db2014b48e69d30f534ef22
Tx public key: 90a2f4d164879f51fb731fddad46aa3911a2f7667e81e7c4c06b98793ab04fb4
Timestamp: 1761787755 Timestamp [UCT]: 2025-10-30 01:29:15 Age [y:d:h:m:s]: 00:067:18:55:51
Block: 1400891 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 48541 RingCT/type: yes/0
Extra: 0190a2f4d164879f51fb731fddad46aa3911a2f7667e81e7c4c06b98793ab04fb402110000000925a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3cc7ddb7b949f112cb920074599bf967118a766d3830f822a514a54b1e8b701b 0.600000000000 1889210 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": 1400901, "vin": [ { "gen": { "height": 1400891 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3cc7ddb7b949f112cb920074599bf967118a766d3830f822a514a54b1e8b701b" } } ], "extra": [ 1, 144, 162, 244, 209, 100, 135, 159, 81, 251, 115, 31, 221, 173, 70, 170, 57, 17, 162, 247, 102, 126, 129, 231, 196, 192, 107, 152, 121, 58, 176, 79, 180, 2, 17, 0, 0, 0, 9, 37, 163, 90, 15, 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