Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fce1842c9138b81b0c596b36ef546b516ae2fc1a3d2dc2d8e1823a42b799205c

Tx prefix hash: e0c1587f0bd926d2a0745dc21af9570ce91609b7030ef73856e50897616a7212
Tx public key: b62669401c0dfa0da832a71ab6478ef122348d8b012dd00e2c23657cbe1ee434
Timestamp: 1740530247 Timestamp [UTC]: 2025-02-26 00:37:27 Age [y:d:h:m:s]: 01:073:06:20:08
Block: 1227291 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 303634 RingCT/type: yes/0
Extra: 01b62669401c0dfa0da832a71ab6478ef122348d8b012dd00e2c23657cbe1ee4340211000000051f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 279ee75f266aa8c2be8d9d008f95395bae0bddce88cc7ea7f1eb9649700a3421 0.000600000000 1714164 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": 1227301, "vin": [ { "gen": { "height": 1227291 } } ], "vout": [ { "amount": 600000000, "target": { "key": "279ee75f266aa8c2be8d9d008f95395bae0bddce88cc7ea7f1eb9649700a3421" } } ], "extra": [ 1, 182, 38, 105, 64, 28, 13, 250, 13, 168, 50, 167, 26, 182, 71, 142, 241, 34, 52, 141, 139, 1, 45, 208, 14, 44, 35, 101, 124, 190, 30, 228, 52, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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: