Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 29d29efe01973d34bce8ba5c32884893ce6f1fb9d70374f6cd49255ef64bc927

Tx prefix hash: 5e4617c5b06566bbe373537fff66d7eab6b58d41e9c44b00b7f50d710c2a6a83
Tx public key: 5df3a1fee8574bfda165324e410d385aea3b277efba8cff4610be43433a7ac04
Timestamp: 1757322332 Timestamp [UTC]: 2025-09-08 09:05:32 Age [y:d:h:m:s]: 01:072:22:56:08
Block: 1363959 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 318567 RingCT/type: yes/0
Extra: 015df3a1fee8574bfda165324e410d385aea3b277efba8cff4610be43433a7ac04021100000003b2f784c4000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 485ee0ae3ac0ab5d93053a5d5c4779342ba2598806edb244e7e8eea97ed8b6f5 0.000600000000 1851998 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": 1363969, "vin": [ { "gen": { "height": 1363959 } } ], "vout": [ { "amount": 600000000, "target": { "key": "485ee0ae3ac0ab5d93053a5d5c4779342ba2598806edb244e7e8eea97ed8b6f5" } } ], "extra": [ 1, 93, 243, 161, 254, 232, 87, 75, 253, 161, 101, 50, 78, 65, 13, 56, 90, 234, 59, 39, 126, 251, 168, 207, 244, 97, 11, 228, 52, 51, 167, 172, 4, 2, 17, 0, 0, 0, 3, 178, 247, 132, 196, 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: