Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 25aa206b0ee48e3e239b7e84adda2b790aa72a3717ff8b1bb695e77a7b5ee454

Tx prefix hash: 02a8546d2ffd1f37aa1484157e96a4ecb816855df1750b4c8e63bcfe8ba4b92a
Tx public key: c4fc16b5f3ef795079220985fb1cf537c3e39aa91366e23de30975f3a858dc14
Timestamp: 1678001986 Timestamp [UTC]: 2023-03-05 07:39:46 Age [y:d:h:m:s]: 03:072:11:59:17
Block: 710263 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 824314 RingCT/type: yes/0
Extra: 01c4fc16b5f3ef795079220985fb1cf537c3e39aa91366e23de30975f3a858dc1402110000000374b6d784000000000000000000

1 output(s) for total of 0.002720218156 xmr

stealth address amount amount idx tag
00: 5e60a5bf2c47783b02f2aa140b4f1d1ddb3b4c70b272aa0d87305f9316c35e5e 0.002720218156 1154302 of 0 -

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": 710273, "vin": [ { "gen": { "height": 710263 } } ], "vout": [ { "amount": 2720218156, "target": { "key": "5e60a5bf2c47783b02f2aa140b4f1d1ddb3b4c70b272aa0d87305f9316c35e5e" } } ], "extra": [ 1, 196, 252, 22, 181, 243, 239, 121, 80, 121, 34, 9, 133, 251, 28, 245, 55, 195, 227, 154, 169, 19, 102, 226, 61, 227, 9, 117, 243, 168, 88, 220, 20, 2, 17, 0, 0, 0, 3, 116, 182, 215, 132, 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: