Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bdc7a0a1aa88e12fe890a30e3fb62ef2b3353f51cc52fe6dbddaece7df20ade1

Tx prefix hash: e71582dc6c0faf6de24038f076a1c9fb697dd0b10a0d3e10134856a47761b538
Tx public key: 74342812f656cb52a54f9d5d3fd73cfa04699f87578147cad7bd9f10d31ba7a2
Timestamp: 1711855182 Timestamp [UTC]: 2024-03-31 03:19:42 Age [y:d:h:m:s]: 01:335:03:59:45
Block: 990050 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 498144 RingCT/type: yes/0
Extra: 0174342812f656cb52a54f9d5d3fd73cfa04699f87578147cad7bd9f10d31ba7a20211000000020011055b000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: dc9b9f2d4600c6e1f3d3939cfdf0f20e5b842a5f142aca8f11d0041ea0e1df77 0.000600000000 1450370 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": 990060, "vin": [ { "gen": { "height": 990050 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dc9b9f2d4600c6e1f3d3939cfdf0f20e5b842a5f142aca8f11d0041ea0e1df77" } } ], "extra": [ 1, 116, 52, 40, 18, 246, 86, 203, 82, 165, 79, 157, 93, 63, 215, 60, 250, 4, 105, 159, 135, 87, 129, 71, 202, 215, 189, 159, 16, 211, 27, 167, 162, 2, 17, 0, 0, 0, 2, 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) | dinastycoin version: tesla-369