Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fb47f144e8ccf3d7d6a673241cbe623675fa913d8fdbc3d0ed393536d4a111ac

Tx prefix hash: ac1a30208516cb0aac248c9c7ad9581149aeb4effb4bd40ae632baeeca7aa463
Tx public key: e4e9becca0b9d7bbc4622e1d879d5e54edb5b5552536ad12b94085949b7f309a
Timestamp: 1744811486 Timestamp [UTC]: 2025-04-16 13:51:26 Age [y:d:h:m:s]: 01:088:00:49:20
Block: 1262748 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 318668 RingCT/type: yes/0
Extra: 01e4e9becca0b9d7bbc4622e1d879d5e54edb5b5552536ad12b94085949b7f309a0211000000046c98aa3d000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 1c056bf8a6114e7acf0f4e2dc4cb618b4ac9f9df155fb7059644ad063432a5c1 0.000600000000 1749931 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": 1262758, "vin": [ { "gen": { "height": 1262748 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1c056bf8a6114e7acf0f4e2dc4cb618b4ac9f9df155fb7059644ad063432a5c1" } } ], "extra": [ 1, 228, 233, 190, 204, 160, 185, 215, 187, 196, 98, 46, 29, 135, 157, 94, 84, 237, 181, 181, 85, 37, 54, 173, 18, 185, 64, 133, 148, 155, 127, 48, 154, 2, 17, 0, 0, 0, 4, 108, 152, 170, 61, 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: