Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ce7d572359b588bfdb9b860c6621094bde5914960616167bc4395e4c0d21b791

Tx prefix hash: d104d50e5b3e05cc73f074ffd06d97bc24dfe26e12ec3c260571e11f834429b8
Tx public key: 456fce8eeb213ea1e29378fd82b4fd54266df74e7f6a25c3fc22af779396d5c8
Timestamp: 1747781922 Timestamp [UCT]: 2025-05-20 22:58:42 Age [y:d:h:m:s]: 00:183:23:29:17
Block: 1287353 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 129177 RingCT/type: yes/0
Extra: 01456fce8eeb213ea1e29378fd82b4fd54266df74e7f6a25c3fc22af779396d5c80211000000041f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 46c925b5e53860bb6919fffea4c7bdbe0c481687f77033ba1f5d7e17729b861d 0.600000000000 1774820 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": 1287363, "vin": [ { "gen": { "height": 1287353 } } ], "vout": [ { "amount": 600000000, "target": { "key": "46c925b5e53860bb6919fffea4c7bdbe0c481687f77033ba1f5d7e17729b861d" } } ], "extra": [ 1, 69, 111, 206, 142, 235, 33, 62, 161, 226, 147, 120, 253, 130, 180, 253, 84, 38, 109, 247, 78, 127, 106, 37, 195, 252, 34, 175, 119, 147, 150, 213, 200, 2, 17, 0, 0, 0, 4, 31, 144, 81, 122, 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