Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4f6cd6b33fa8e1743f94a5ff6c51f1257cde6a6a9591aaeaa79ef19a5e6eac7d

Tx prefix hash: 9fd2b400821ef8dca12b058c45bf0ce7bff0d12b86abdc2c0140747a7b6e4f36
Tx public key: 838959a7d842b1854dbe330bbf2500b09ae5086136895b89095919a08b76223f
Timestamp: 1683647240 Timestamp [UTC]: 2023-05-09 15:47:20 Age [y:d:h:m:s]: 03:194:06:18:19
Block: 756435 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 924989 RingCT/type: yes/0
Extra: 01838959a7d842b1854dbe330bbf2500b09ae5086136895b89095919a08b76223f021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.001912568627 xmr

stealth address amount amount idx tag
00: 07bb7fb36f44e8c03453a84fd47ddd9ab58d511d166dbac4933bde38575b029c 0.001912568627 1204814 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": 756445, "vin": [ { "gen": { "height": 756435 } } ], "vout": [ { "amount": 1912568627, "target": { "key": "07bb7fb36f44e8c03453a84fd47ddd9ab58d511d166dbac4933bde38575b029c" } } ], "extra": [ 1, 131, 137, 89, 167, 216, 66, 177, 133, 77, 190, 51, 11, 191, 37, 0, 176, 154, 229, 8, 97, 54, 137, 91, 137, 9, 89, 25, 160, 139, 118, 34, 63, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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: