Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 345527dcbd1853239d2480b1718fed21b044e5e9728ab22311f691de0735270b

Tx prefix hash: 8d573c6b405c48da7eb069f05d4998eedc871f48cd3b9924860e9ad693d0205a
Tx public key: 2bb707030d25b058d0d7d81382d0e8e6ae2d170a7efb6f1913c533baffef38b0
Timestamp: 1751159320 Timestamp [UCT]: 2025-06-29 01:08:40 Age [y:d:h:m:s]: 00:150:13:42:31
Block: 1314883 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105721 RingCT/type: yes/0
Extra: 012bb707030d25b058d0d7d81382d0e8e6ae2d170a7efb6f1913c533baffef38b0021100000003bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 82296fcabef226e81f96a3c95fcd47fe25aff117989afb302aec4162f2debe48 0.600000000000 1802536 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": 1314893, "vin": [ { "gen": { "height": 1314883 } } ], "vout": [ { "amount": 600000000, "target": { "key": "82296fcabef226e81f96a3c95fcd47fe25aff117989afb302aec4162f2debe48" } } ], "extra": [ 1, 43, 183, 7, 3, 13, 37, 176, 88, 208, 215, 216, 19, 130, 208, 232, 230, 174, 45, 23, 10, 126, 251, 111, 25, 19, 197, 51, 186, 255, 239, 56, 176, 2, 17, 0, 0, 0, 3, 191, 81, 178, 162, 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