Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c73e38794ddd7d6a07778a491cf2434c2b651f47faa363df1bbf0b94d49bcba1

Tx prefix hash: 3ad1fc7d79f384bb76a69716ee6e42af6f38ac11c8b89c20212b787407391e2c
Tx public key: 6e4ee1dfdad50e90f2054781a2592e1b02d79785b31840a8a080a639318a60db
Timestamp: 1709529741 Timestamp [UTC]: 2024-03-04 05:22:21 Age [y:d:h:m:s]: 02:260:22:20:27
Block: 970760 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 711614 RingCT/type: yes/0
Extra: 016e4ee1dfdad50e90f2054781a2592e1b02d79785b31840a8a080a639318a60db0211000000030011055b000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 4609258db2bb91df2647149e7b8d81a0d1d9c68fc341dbc8945847f3e7d25cd1 0.000600000000 1430621 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": 970770, "vin": [ { "gen": { "height": 970760 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4609258db2bb91df2647149e7b8d81a0d1d9c68fc341dbc8945847f3e7d25cd1" } } ], "extra": [ 1, 110, 78, 225, 223, 218, 213, 14, 144, 242, 5, 71, 129, 162, 89, 46, 27, 2, 215, 151, 133, 179, 24, 64, 168, 160, 128, 166, 57, 49, 138, 96, 219, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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: