Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cd1a4840de4c425421d17d217915302f86bcb680d6f4dcbdd93ba75e7ec6b4d6

Tx prefix hash: 336b728134db282075168aedd641993e585a034ba37bdeca44ce5669403ff23c
Tx public key: 7e1ef134d9c6c2b2b6b839e918d4eb10be38816849405b131a8317211338b586
Timestamp: 1754780135 Timestamp [UTC]: 2025-08-09 22:55:35 Age [y:d:h:m:s]: 01:099:20:07:43
Block: 1343768 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 336809 RingCT/type: yes/0
Extra: 017e1ef134d9c6c2b2b6b839e918d4eb10be38816849405b131a8317211338b5860211000000022609b3a0000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: cdf31e2350db2f178db1b8fdb6612273cf2a271adca2e37e4e55a75d1e2b5d95 0.000600000000 1831609 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": 1343778, "vin": [ { "gen": { "height": 1343768 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cdf31e2350db2f178db1b8fdb6612273cf2a271adca2e37e4e55a75d1e2b5d95" } } ], "extra": [ 1, 126, 30, 241, 52, 217, 198, 194, 178, 182, 184, 57, 233, 24, 212, 235, 16, 190, 56, 129, 104, 73, 64, 91, 19, 26, 131, 23, 33, 19, 56, 181, 134, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 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: