Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8d28a781555f5ece1be0d1a658e92e2bbb9af2bd4435ddf121fb3bf48eb1b0b9

Tx prefix hash: fa531022a38a70db313247a4d20de6d8a22294e3c00431432806f73fedee02db
Tx public key: 58755e972f25da9e75cac12474db86811ad13b139d12df7e0b970e3b98fef877
Timestamp: 1743988783 Timestamp [UTC]: 2025-04-07 01:19:43 Age [y:d:h:m:s]: 01:221:17:01:28
Block: 1255924 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 422397 RingCT/type: yes/0
Extra: 0158755e972f25da9e75cac12474db86811ad13b139d12df7e0b970e3b98fef877021100000002dbb571c1000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: f5f3b888550643f908c8ed371cc3d46b9ae4ad73f5179a7b593eb59248a8f7e1 0.000600000000 1743031 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": 1255934, "vin": [ { "gen": { "height": 1255924 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f5f3b888550643f908c8ed371cc3d46b9ae4ad73f5179a7b593eb59248a8f7e1" } } ], "extra": [ 1, 88, 117, 94, 151, 47, 37, 218, 158, 117, 202, 193, 36, 116, 219, 134, 129, 26, 209, 59, 19, 157, 18, 223, 126, 11, 151, 14, 59, 152, 254, 248, 119, 2, 17, 0, 0, 0, 2, 219, 181, 113, 193, 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: