Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4fb265f4f099337191a47fc0ea496734074a37a3eb826378f74a52cbcca52fb3

Tx prefix hash: f8fd0f6cdaea9e3c1ae48268904ca954506cd6382dc956f8ba41dec236bd0d2e
Tx public key: 5cfa4ec5988c7048c3b43d73bd1671911b1d341e513d93f137c309b6f23cfd8d
Timestamp: 1765899404 Timestamp [UTC]: 2025-12-16 15:36:44 Age [y:d:h:m:s]: 00:144:18:37:18
Block: 1434939 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 96077 RingCT/type: yes/0
Extra: 015cfa4ec5988c7048c3b43d73bd1671911b1d341e513d93f137c309b6f23cfd8d021100000005d6e19d7c000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 22974274efbdf5178fc0355112df2718a5bb2d6eb1842df0a7c86b415dcac3e1 0.000600000000 1923736 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 dinastycoin-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": 1434949, "vin": [ { "gen": { "height": 1434939 } } ], "vout": [ { "amount": 600000000, "target": { "key": "22974274efbdf5178fc0355112df2718a5bb2d6eb1842df0a7c86b415dcac3e1" } } ], "extra": [ 1, 92, 250, 78, 197, 152, 140, 112, 72, 195, 180, 61, 115, 189, 22, 113, 145, 27, 29, 52, 30, 81, 61, 147, 241, 55, 195, 9, 182, 242, 60, 253, 141, 2, 17, 0, 0, 0, 5, 214, 225, 157, 124, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: