Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b70e4cdb5cd01e9c20d1fc44b8fb4a357f9360fc4764f5d3d099e2e978629320

Tx prefix hash: 6640c4d3f166f5cecaaa119e7d53668085230a0672db3f7db020de43d7118945
Tx public key: cc1b1bcfa25cb0bb3bdb991cd4bf6c3a5377f31c2b1bd8cce345b3a3d271aab6
Timestamp: 1766766256 Timestamp [UTC]: 2025-12-26 16:24:16 Age [y:d:h:m:s]: 00:206:06:15:02
Block: 1442133 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 140981 RingCT/type: yes/0
Extra: 01cc1b1bcfa25cb0bb3bdb991cd4bf6c3a5377f31c2b1bd8cce345b3a3d271aab602110000000ad6e19d7c000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: fcec3c04ede0336a365e49fbb1cf40eea1dfe588774f44a7deb2ca5b7810805b 0.000600000000 1931032 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": 1442143, "vin": [ { "gen": { "height": 1442133 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fcec3c04ede0336a365e49fbb1cf40eea1dfe588774f44a7deb2ca5b7810805b" } } ], "extra": [ 1, 204, 27, 27, 207, 162, 92, 176, 187, 59, 219, 153, 28, 212, 191, 108, 58, 83, 119, 243, 28, 43, 27, 216, 204, 227, 69, 179, 163, 210, 113, 170, 182, 2, 17, 0, 0, 0, 10, 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: