Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f1b3865f913e0f2e179d261b3ccf3050a616f1ea2af9100b142b3c74251a1c2

Tx prefix hash: 7d7d466df09a3b2093e8d22c0f2a73b53fb49ac234f4ad8f5078a7d2ba3f5049
Tx public key: 4056b60939be02af816594533eab40e036e1b7aa1d52f0ba40448de894b8180b
Timestamp: 1713903796 Timestamp [UTC]: 2024-04-23 20:23:16 Age [y:d:h:m:s]: 02:211:20:56:04
Block: 1007014 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 676480 RingCT/type: yes/0
Extra: 014056b60939be02af816594533eab40e036e1b7aa1d52f0ba40448de894b8180b02110000000259dad3f5000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 5ecbcb61a1a023ede057d274e3cee91f9fac3529239d923c687e77e16bd01888 0.000600000000 1468224 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": 1007024, "vin": [ { "gen": { "height": 1007014 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5ecbcb61a1a023ede057d274e3cee91f9fac3529239d923c687e77e16bd01888" } } ], "extra": [ 1, 64, 86, 182, 9, 57, 190, 2, 175, 129, 101, 148, 83, 62, 171, 64, 224, 54, 225, 183, 170, 29, 82, 240, 186, 64, 68, 141, 232, 148, 184, 24, 11, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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: