Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 58779ff89bfb1b77bda3f4c9a06c9020bd95bab9ffc48dd00b1927cc0f9cb4a4

Tx prefix hash: f55bc11d87642fdcd661722704efd1c875577d6c34d64f5d34f80bd1085fb4f4
Tx public key: 447c756a22ec3e6d77f00927ca7f630ee1b1533af9f03e08479770eb10560554
Timestamp: 1585415493 Timestamp [UTC]: 2020-03-28 17:11:33 Age [y:d:h:m:s]: 06:053:02:22:01
Block: 88817 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1449653 RingCT/type: yes/0
Extra: 01447c756a22ec3e6d77f00927ca7f630ee1b1533af9f03e08479770eb105605540211000002e386362411000000000000000000

1 output(s) for total of 0.311683050929 xmr

stealth address amount amount idx tag
00: 6dfa931e3c55730229edff0fc634e22e3c5272d73380d42a5bbc054a8e6912f4 0.311683050929 159591 of 0 -

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": 88827, "vin": [ { "gen": { "height": 88817 } } ], "vout": [ { "amount": 311683050929, "target": { "key": "6dfa931e3c55730229edff0fc634e22e3c5272d73380d42a5bbc054a8e6912f4" } } ], "extra": [ 1, 68, 124, 117, 106, 34, 236, 62, 109, 119, 240, 9, 39, 202, 127, 99, 14, 225, 177, 83, 58, 249, 240, 62, 8, 71, 151, 112, 235, 16, 86, 5, 84, 2, 17, 0, 0, 2, 227, 134, 54, 36, 17, 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: