Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 50d71cce2426fdc57f7431038bf18d3cebb032260279d135f75f3f17534d8c74

Tx prefix hash: bbfa6e85230fd090455bc23f8e98b52a7402d3cd35a35f8f8b07fc4defb5e7d7
Tx public key: f0338cc19a435496331346d950072ffe5927240c0ccc3916754c7e4a91fa4d06
Timestamp: 1769241140 Timestamp [UTC]: 2026-01-24 07:52:20 Age [y:d:h:m:s]: 00:022:20:19:48
Block: 1462466 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 16338 RingCT/type: yes/0
Extra: 01f0338cc19a435496331346d950072ffe5927240c0ccc3916754c7e4a91fa4d0602110000000c49d73e98000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 8d7dafc60fd9f1a71d9afb2ce2958a5cbb7672414f74ec75c15e972b62de6a58 0.000600000000 1951664 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": 1462476, "vin": [ { "gen": { "height": 1462466 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8d7dafc60fd9f1a71d9afb2ce2958a5cbb7672414f74ec75c15e972b62de6a58" } } ], "extra": [ 1, 240, 51, 140, 193, 154, 67, 84, 150, 51, 19, 70, 217, 80, 7, 47, 254, 89, 39, 36, 12, 12, 204, 57, 22, 117, 76, 126, 74, 145, 250, 77, 6, 2, 17, 0, 0, 0, 12, 73, 215, 62, 152, 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