Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 26ddc41b191bd24297676cfa7289f5dfbae30c72a2838d7e04dfb021007d8097

Tx prefix hash: 660e3ab4540a59e2d2b5ff179408b12d2b1c64b7e34f3eb434b585d12b46865b
Tx public key: b6fd4eef393b782fd08daa4f188eead22b4a2419fbc846fdc7876d916342e17d
Timestamp: 1702124387 Timestamp [UTC]: 2023-12-09 12:19:47 Age [y:d:h:m:s]: 02:349:09:04:17
Block: 909350 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 774800 RingCT/type: yes/0
Extra: 01b6fd4eef393b782fd08daa4f188eead22b4a2419fbc846fdc7876d916342e17d0211000000014b8f5122000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: e86bdf4ba97267fd4b2e3ccf8d4b39501ae2dce51add25be6153b687f86cc90a 0.000600000000 1366431 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": 909360, "vin": [ { "gen": { "height": 909350 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e86bdf4ba97267fd4b2e3ccf8d4b39501ae2dce51add25be6153b687f86cc90a" } } ], "extra": [ 1, 182, 253, 78, 239, 57, 59, 120, 47, 208, 141, 170, 79, 24, 142, 234, 210, 43, 74, 36, 25, 251, 200, 70, 253, 199, 135, 109, 145, 99, 66, 225, 125, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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: