Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 523d2e9f0c33bfe41388ab3e5109314adc883962e23ab7e8bc7de7c366161c2f

Tx prefix hash: 642982c585a0077015b5fbd37e646182261a0d779ad15230730d5be1657598a8
Tx public key: 5a1cc513fd06cd6e46ad84b5beee7fb668b0c71f2d2e4eb2a2f3c85b9b529929
Timestamp: 1761756532 Timestamp [UCT]: 2025-10-29 16:48:52 Age [y:d:h:m:s]: 00:068:05:57:23
Block: 1400632 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 48875 RingCT/type: yes/0
Extra: 015a1cc513fd06cd6e46ad84b5beee7fb668b0c71f2d2e4eb2a2f3c85b9b52992902110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: baf059e1c5b54229e76a05cc06686d8e8ea7ad46c2e0a2c91d1d12c13f4a8ba1 0.600000000000 1888949 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": 1400642, "vin": [ { "gen": { "height": 1400632 } } ], "vout": [ { "amount": 600000000, "target": { "key": "baf059e1c5b54229e76a05cc06686d8e8ea7ad46c2e0a2c91d1d12c13f4a8ba1" } } ], "extra": [ 1, 90, 28, 197, 19, 253, 6, 205, 110, 70, 173, 132, 181, 190, 238, 127, 182, 104, 176, 199, 31, 45, 46, 78, 178, 162, 243, 200, 91, 155, 82, 153, 41, 2, 17, 0, 0, 0, 1, 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