Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 82489ead206e55dd759904327a3257aee1db3deb53bf6a73c02c0433bf2f2f68

Tx prefix hash: ea4de2dcd2f572784746769af12ff4443dcdfcd05d41666da128f4df4f92b68c
Tx public key: 501e0fa86c7c536c1f121da3ec057b67025d7d8016ee9e7ebb5ae40adff6c3be
Timestamp: 1737811068 Timestamp [UTC]: 2025-01-25 13:17:48 Age [y:d:h:m:s]: 01:110:15:26:00
Block: 1205020 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 329852 RingCT/type: yes/0
Extra: 01501e0fa86c7c536c1f121da3ec057b67025d7d8016ee9e7ebb5ae40adff6c3be021100000005007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a58aab84cbe1096a095bc1b96f40eb01ae2822b1561ab04fa8af94e8a34e8870 0.000600000000 1691715 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": 1205030, "vin": [ { "gen": { "height": 1205020 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a58aab84cbe1096a095bc1b96f40eb01ae2822b1561ab04fa8af94e8a34e8870" } } ], "extra": [ 1, 80, 30, 15, 168, 108, 124, 83, 108, 31, 18, 29, 163, 236, 5, 123, 103, 2, 93, 125, 128, 22, 238, 158, 126, 187, 90, 228, 10, 223, 246, 195, 190, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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: