Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2b3be5bd5bbbaf7f9631872a1a80fc95d56d90dec4b54dbaf064e848c840cf7f

Tx prefix hash: 139e19ebea4d8e42a8bdca867f099f463eb21a28cb968a66e92907576ad4768d
Tx public key: 74bde5397d2f493e9142c94fc0b96e4bf2ae758861f3bac59bfd3317cf4bdf07
Timestamp: 1742397739 Timestamp [UCT]: 2025-03-19 15:22:19 Age [y:d:h:m:s]: 00:293:04:10:31
Block: 1242785 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 207320 RingCT/type: yes/0
Extra: 0174bde5397d2f493e9142c94fc0b96e4bf2ae758861f3bac59bfd3317cf4bdf07021100000008f7071dc6000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aec7261a9c596a1aab39fd7238e8887b3851288d4ae1a2f1360f87532ebcfa69 0.600000000000 1729762 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": 1242795, "vin": [ { "gen": { "height": 1242785 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aec7261a9c596a1aab39fd7238e8887b3851288d4ae1a2f1360f87532ebcfa69" } } ], "extra": [ 1, 116, 189, 229, 57, 125, 47, 73, 62, 145, 66, 201, 79, 192, 185, 110, 75, 242, 174, 117, 136, 97, 243, 186, 197, 155, 253, 51, 23, 207, 75, 223, 7, 2, 17, 0, 0, 0, 8, 247, 7, 29, 198, 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