Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a4b2053d5590cb65b54d871b57f48f72e0d15d4fc517cc398ec03b3795359eeb

Tx prefix hash: 4f1d38aa3388781ea922d6738e3e6e04a0cbc9edfd15942745fac98281abdd99
Tx public key: b9c8eff527b1edd99e32fd3987eaca9f0eaf4e1672c1203654dc7cb0fc62defc
Timestamp: 1751015371 Timestamp [UCT]: 2025-06-27 09:09:31 Age [y:d:h:m:s]: 00:135:12:55:44
Block: 1313773 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 94884 RingCT/type: yes/0
Extra: 01b9c8eff527b1edd99e32fd3987eaca9f0eaf4e1672c1203654dc7cb0fc62defc021100000003d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bcceb839ecb9779b927bdef31b8ff22545925415ddeb56e01920052f231602b7 0.600000000000 1801416 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": 1313783, "vin": [ { "gen": { "height": 1313773 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bcceb839ecb9779b927bdef31b8ff22545925415ddeb56e01920052f231602b7" } } ], "extra": [ 1, 185, 200, 239, 245, 39, 177, 237, 217, 158, 50, 253, 57, 135, 234, 202, 159, 14, 175, 78, 22, 114, 193, 32, 54, 84, 220, 124, 176, 252, 98, 222, 252, 2, 17, 0, 0, 0, 3, 216, 231, 210, 65, 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