Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bed0c0019e2bcd135e5263be72566162bbfd846c1d5568d448f40e0c8a77b29f

Tx prefix hash: 798ceb2a55abb3c4ef86e885d0e681f9077a10d92aa8851a84a9273b36939f4c
Tx public key: 61704c99cdf518818d5529272e030355f59fbe3f9fd4a3ed124a709ad3ebc0f2
Timestamp: 1772135333 Timestamp [UTC]: 2026-02-26 19:48:53 Age [y:d:h:m:s]: 00:263:10:10:10
Block: 1486412 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 193772 RingCT/type: yes/0
Extra: 0161704c99cdf518818d5529272e030355f59fbe3f9fd4a3ed124a709ad3ebc0f2021100000004e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 32f34c7b26588a85fccc70e356fbdef5aff557b136b81f60b27ef88007cfb1a5 0.000600000000 1975866 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": 1486422, "vin": [ { "gen": { "height": 1486412 } } ], "vout": [ { "amount": 600000000, "target": { "key": "32f34c7b26588a85fccc70e356fbdef5aff557b136b81f60b27ef88007cfb1a5" } } ], "extra": [ 1, 97, 112, 76, 153, 205, 245, 24, 129, 141, 85, 41, 39, 46, 3, 3, 85, 245, 159, 190, 63, 159, 212, 163, 237, 18, 74, 112, 154, 211, 235, 192, 242, 2, 17, 0, 0, 0, 4, 228, 245, 25, 63, 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: