Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f4c08ee92b3d521d236f00bb0f79162be881b338537ed7de8aab52d57b23c8af

Tx prefix hash: e1037f4f61b9decba971d42104f1e5396655495da619b9a95082ed941ea40041
Tx public key: 2c1f11eb61eba354f7b361303b1878a207e91cc6caf33a8140a6974ea7f4768a
Timestamp: 1771177948 Timestamp [UTC]: 2026-02-15 17:52:28 Age [y:d:h:m:s]: 00:101:16:46:01
Block: 1478492 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66763 RingCT/type: yes/0
Extra: 012c1f11eb61eba354f7b361303b1878a207e91cc6caf33a8140a6974ea7f4768a021100000006e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 9b3ffbc5adbdacf178de24274e845bacc9a8e671bfc4f1fd3cefcdc963e8fb70 0.000600000000 1967822 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": 1478502, "vin": [ { "gen": { "height": 1478492 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9b3ffbc5adbdacf178de24274e845bacc9a8e671bfc4f1fd3cefcdc963e8fb70" } } ], "extra": [ 1, 44, 31, 17, 235, 97, 235, 163, 84, 247, 179, 97, 48, 59, 24, 120, 162, 7, 233, 28, 198, 202, 243, 58, 129, 64, 166, 151, 78, 167, 244, 118, 138, 2, 17, 0, 0, 0, 6, 228, 245, 25, 63, 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: