Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3ff3fdf8379ff355355a4f131cb658350433a1ded2ebd7a75a80f42accbe3bba

Tx prefix hash: c7d1d25cdc0d08bbcf69d8ed01443791206edc2448b30a2ea1ca4ce1e0289c1f
Tx public key: ce21811f2d158f308691231b388e504c5d429248386411043c3435001570ec8a
Timestamp: 1742683429 Timestamp [UTC]: 2025-03-22 22:43:49 Age [y:d:h:m:s]: 00:333:00:44:23
Block: 1245130 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 235683 RingCT/type: yes/0
Extra: 01ce21811f2d158f308691231b388e504c5d429248386411043c3435001570ec8a0211000000022609b3a0000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: ed72f317ccf596c0a8fafc2aacd5f4aa019bc31d52441fb547b3c4141219c9f3 0.000600000000 1732121 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": 1245140, "vin": [ { "gen": { "height": 1245130 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ed72f317ccf596c0a8fafc2aacd5f4aa019bc31d52441fb547b3c4141219c9f3" } } ], "extra": [ 1, 206, 33, 129, 31, 45, 21, 143, 48, 134, 145, 35, 27, 56, 142, 80, 76, 93, 66, 146, 72, 56, 100, 17, 4, 60, 52, 53, 0, 21, 112, 236, 138, 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) | dinastycoin version: tesla-369