Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4da74c368ff654904cfcd31950fe9eaf69098e91ad8f124f5e3e5454be06d273

Tx prefix hash: 306a4f28dd8d79d03ebfd893c37cf337f3963029ecf6a5e98018d018a1d6612a
Tx public key: 5ffbeba0ee1b37f2ca9bd2c52420b624ca50b06e9993fb973be0d0bfb4b994c9
Timestamp: 1572882425 Timestamp [UTC]: 2019-11-04 15:47:05 Age [y:d:h:m:s]: 07:020:06:01:57
Block: 680 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0801 kB
Tx version: 2 No of confirmations: 1683470 RingCT/type: yes/0
Extra: 015ffbeba0ee1b37f2ca9bd2c52420b624ca50b06e9993fb973be0d0bfb4b994c9

1 output(s) for total of 0.610587322452 xmr

stealth address amount amount idx tag
00: f50690cac1af41277e28cd481e2e2a826b44016b3ad60d2b8bd2c81e688c6bd9 0.610587322452 634 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": 690, "vin": [ { "gen": { "height": 680 } } ], "vout": [ { "amount": 610587322452, "target": { "key": "f50690cac1af41277e28cd481e2e2a826b44016b3ad60d2b8bd2c81e688c6bd9" } } ], "extra": [ 1, 95, 251, 235, 160, 238, 27, 55, 242, 202, 155, 210, 197, 36, 32, 182, 36, 202, 80, 176, 110, 153, 147, 251, 151, 59, 224, 208, 191, 180, 185, 148, 201 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: