Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: deb9c0c29432785b723d72ba137d946feb6568add5c2ba9beeeb76cc1a8a9178

Tx prefix hash: 1c23a279b39ae5f951d4439c03d6e31525596db1d37bea6f45b41f0fc9dd18ee
Tx public key: ff6f1de72106e5c0f186154f86d58236752b0550d5d776c89d49497bb5d52dde
Timestamp: 1751720180 Timestamp [UCT]: 2025-07-05 12:56:20 Age [y:d:h:m:s]: 00:187:16:56:32
Block: 1319265 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 132582 RingCT/type: yes/0
Extra: 01ff6f1de72106e5c0f186154f86d58236752b0550d5d776c89d49497bb5d52dde02110000000225a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4c504006e410cda7c6596f729ed9c3337a0ae3908caa957b3c935617cdf6046f 0.600000000000 1806956 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": 1319275, "vin": [ { "gen": { "height": 1319265 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4c504006e410cda7c6596f729ed9c3337a0ae3908caa957b3c935617cdf6046f" } } ], "extra": [ 1, 255, 111, 29, 231, 33, 6, 229, 192, 241, 134, 21, 79, 134, 213, 130, 54, 117, 43, 5, 80, 213, 215, 118, 200, 157, 73, 73, 123, 181, 213, 45, 222, 2, 17, 0, 0, 0, 2, 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