Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a125d1ecec1b37b0c48fa06e0bf92b976dcfbe0d9d74bc78277676426f93722

Tx prefix hash: 2a52a58ca79e17b1d724ea4a98c74bd8d67a13fa1bebb28a1448c6b0515ceb35
Tx public key: a35c33357d689de874a4e593309e76d704b2affbe41186b5a09cf0b46eb31218
Timestamp: 1735685390 Timestamp [UCT]: 2024-12-31 22:49:50 Age [y:d:h:m:s]: 00:090:22:28:48
Block: 1187462 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 64765 RingCT/type: yes/0
Extra: 01a35c33357d689de874a4e593309e76d704b2affbe41186b5a09cf0b46eb312180211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 25c7aae03010a69393a8433f87846346d1c88b2cb7b467aa5548022dc66ac8f0 0.600000000000 1673953 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": 1187472, "vin": [ { "gen": { "height": 1187462 } } ], "vout": [ { "amount": 600000000, "target": { "key": "25c7aae03010a69393a8433f87846346d1c88b2cb7b467aa5548022dc66ac8f0" } } ], "extra": [ 1, 163, 92, 51, 53, 125, 104, 157, 232, 116, 164, 229, 147, 48, 158, 118, 215, 4, 178, 175, 251, 228, 17, 134, 181, 160, 156, 240, 180, 110, 179, 18, 24, 2, 17, 0, 0, 0, 7, 31, 10, 83, 235, 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