Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6d2dbbca4a862a26eebb325aea3fb0b9824e7e87b984c337aeec075f2e430bc2

Tx prefix hash: b1c7b84a1d47f8741a1b53c7c069c386b17229223de43f6433573f516235076c
Tx public key: a2f6b246e832235b03232b5d03a147ad77fa1b0606e7481178fdb86073028418
Timestamp: 1741151313 Timestamp [UTC]: 2025-03-05 05:08:33 Age [y:d:h:m:s]: 00:349:18:38:19
Block: 1232451 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 247594 RingCT/type: yes/0
Extra: 01a2f6b246e832235b03232b5d03a147ad77fa1b0606e7481178fdb860730284180211000000071f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: d2e6b0d53177cf7d67ce3bcaa2c274999bae161ca5286c097a7dad99855b8b9c 0.000600000000 1719364 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": 1232461, "vin": [ { "gen": { "height": 1232451 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d2e6b0d53177cf7d67ce3bcaa2c274999bae161ca5286c097a7dad99855b8b9c" } } ], "extra": [ 1, 162, 246, 178, 70, 232, 50, 35, 91, 3, 35, 43, 93, 3, 161, 71, 173, 119, 250, 27, 6, 6, 231, 72, 17, 120, 253, 184, 96, 115, 2, 132, 24, 2, 17, 0, 0, 0, 7, 31, 10, 83, 235, 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