Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b3b341e5d7bcb84e6178b3ab6ce04eea4bd2a70c9def7ffe07609d0246913c27

Tx prefix hash: bfca60f9aac4af2228fae00bd150f46afd8ffd7702c4cdbb311b34ec15baaf56
Tx public key: c8c5b85789c5156c846e0efe14e2bca9b5fdee60f2db5125b823d744328cfc79
Timestamp: 1628841340 Timestamp [UTC]: 2021-08-13 07:55:40 Age [y:d:h:m:s]: 05:098:21:03:42
Block: 313029 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1368621 RingCT/type: yes/0
Extra: 01c8c5b85789c5156c846e0efe14e2bca9b5fdee60f2db5125b823d744328cfc7902110000001e17696b73000000000000000000

1 output(s) for total of 0.056338522063 xmr

stealth address amount amount idx tag
00: d62803bc1677a99c0ce22e2fa9fd84e9b065689f2dce2381c838dd6eb9e014bb 0.056338522063 651334 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": 313039, "vin": [ { "gen": { "height": 313029 } } ], "vout": [ { "amount": 56338522063, "target": { "key": "d62803bc1677a99c0ce22e2fa9fd84e9b065689f2dce2381c838dd6eb9e014bb" } } ], "extra": [ 1, 200, 197, 184, 87, 137, 197, 21, 108, 132, 110, 14, 254, 20, 226, 188, 169, 181, 253, 238, 96, 242, 219, 81, 37, 184, 35, 215, 68, 50, 140, 252, 121, 2, 17, 0, 0, 0, 30, 23, 105, 107, 115, 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: