Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 25cf124b1c7bdefc3d5d475bb18fc86105accd3ef4b66fff1aa4a0cd7f47480d

Tx prefix hash: 35a08fb640ca9e9e8cd156b7ae6008e8c856a5ab6f016dfae092c5de61496c28
Tx public key: 64faed021ef311db2e221de291c31286c800d6e62ea010f31516899e4f810ecb
Timestamp: 1751665992 Timestamp [UCT]: 2025-07-04 21:53:12 Age [y:d:h:m:s]: 00:132:06:52:46
Block: 1318863 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 92849 RingCT/type: yes/0
Extra: 0164faed021ef311db2e221de291c31286c800d6e62ea010f31516899e4f810ecb02110000000143846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 76a799ef2833e961c99d2fc8eea84b33b0e8e8482411bcbf633557e2d52dccda 0.600000000000 1806550 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": 1318873, "vin": [ { "gen": { "height": 1318863 } } ], "vout": [ { "amount": 600000000, "target": { "key": "76a799ef2833e961c99d2fc8eea84b33b0e8e8482411bcbf633557e2d52dccda" } } ], "extra": [ 1, 100, 250, 237, 2, 30, 243, 17, 219, 46, 34, 29, 226, 145, 195, 18, 134, 200, 0, 214, 230, 46, 160, 16, 243, 21, 22, 137, 158, 79, 129, 14, 203, 2, 17, 0, 0, 0, 1, 67, 132, 109, 102, 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