Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 79019507129fedd2be9a75f870da99050d4061380714644013455b479a665d98

Tx prefix hash: 15539bfb0b00ffd1eda06f00b204e449b80305c9b0d97b4e101a1a49e48e7361
Tx public key: d4d1a1f8c275a11200a704b15a1ec2d75340daa02786d5b6d00d88a9fb7977c0
Timestamp: 1751614564 Timestamp [UCT]: 2025-07-04 07:36:04 Age [y:d:h:m:s]: 00:134:18:52:06
Block: 1318472 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 94607 RingCT/type: yes/0
Extra: 01d4d1a1f8c275a11200a704b15a1ec2d75340daa02786d5b6d00d88a9fb7977c0021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1aea79fc743ad8173a7cfc4287873e9d2f7a4b539af4b7b37b4ab2f76c0ed336 0.600000000000 1806153 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": 1318482, "vin": [ { "gen": { "height": 1318472 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1aea79fc743ad8173a7cfc4287873e9d2f7a4b539af4b7b37b4ab2f76c0ed336" } } ], "extra": [ 1, 212, 209, 161, 248, 194, 117, 161, 18, 0, 167, 4, 177, 90, 30, 194, 215, 83, 64, 218, 160, 39, 134, 213, 182, 208, 13, 136, 169, 251, 121, 119, 192, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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